1
18.7 Legacy Series / Should unbound plugin break dhcp-provided dns nameserver on _all_ my subnets?
« on: December 17, 2018, 10:24:01 pm »
Hi,
I have dhcp active on all my subnets. This works well and provides the dns nameserver option for my dhcp clients to point to a couple of non-opnsense nameservers I use internally.
I am now configuring unbound to listen on just a single vlan/subnet.
I spotted this at the bottom of the plugin config page:
This is a pity because it doesn't just provide the nameservers for the vlan I'm targeting (also through ipv6 RAs, not just dhcp as mentioned in the quote) but it overrides my custom dhcp dns nameserver settings for _all_ other scopes.
Is this really necessary? Is it possible to change this behaviour?
Thanks
I have dhcp active on all my subnets. This works well and provides the dns nameserver option for my dhcp clients to point to a couple of non-opnsense nameservers I use internally.
I am now configuring unbound to listen on just a single vlan/subnet.
I spotted this at the bottom of the plugin config page:
Quote
If the DNS Resolver is enabled, the DHCP service (if enabled) will automatically serve the LAN IP address as a DNS server to DHCP clients so they will use the DNS Resolver.
This is a pity because it doesn't just provide the nameservers for the vlan I'm targeting (also through ipv6 RAs, not just dhcp as mentioned in the quote) but it overrides my custom dhcp dns nameserver settings for _all_ other scopes.
Is this really necessary? Is it possible to change this behaviour?
Thanks