Should unbound plugin break dhcp-provided dns nameserver on _all_ my subnets?

[onnieoneone]

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:

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

[CraigHead]

I just noticed this too.
Also, I noticed that this seems to prefer the IPv6 address on the LAN address serving DHCP on IPv4 as the entry for the nameserver. Which doesn't make any sense to me.

[franco]

Unbound gives out its IP so the users can automatically use the upstream servers without knowing them. But you have to change Unbound to forwarding and that's it.

> this seems to prefer the IPv6 address on the LAN address serving DHCP on IPv4 as the entry for the nameserver

I'm not sure what this means?


Cheers,
Franco