Allow adding multiple DDNS update zones to ISC-DHCP configuration #9410
Description
Important notices
Before you add a new report, we ask you kindly to acknowledge the following:
- I have read the contributing guide lines at https://github.com/opnsense/core/blob/master/CONTRIBUTING.md
- I am convinced that my issue is new after having checked both open and closed issues at https://github.com/opnsense/core/issues?q=is%3Aissue
Is your feature request related to a problem? Please describe.
My local network has an uncommon configuration due to how I wanted to segment things. I wanted to use a 16-bit segment for the whole thing, but I wanted multiple 8-bit segments for different purposes: one segment for "servers" and "static devices", another segment for certain types of computers, yet another for remote access VPN clients, and so on.
As a result, the DNS reverse lookup zone doesn't have 3 octets, but 2: instead of using Y.X.W.in-addr.arpa, I have X.W.in-addr.arpa, and then the PTR records within contain the last two octets - i.e. Z.Y IN PTR somename.
While I can certainly and correctly configure the DDNS update zone for the forward lookups (and it's working 100% flawlessly!), I can't do the same for the reverse lookups because that zone is populated automagically by the configuration, and it's created using 3 octets deduced from the IP pool configurations.
The current UI only supports describing the update zone for the forward lookups, and this is the limiting factor.
Describe the solution you like
Ideally, the solution would allow for selectively disabling the automatic generation of the DDNS update zone for reverse-lookups, and then allow for defining additional custom DDNS update zones which one could then configure accordingly.
Describe alternatives you considered
There is unfortunately no reliable alternative available to me as this would entail manual modification of the generated DHCPD configuration each time, which is a no-no!
Additional context
As you can see, the UI only supports defining a single DDNS update zone, and automatically deduces the reverse lookup zone based on the IP pool's range:
