Unbound issues with DHCP, DNS forwarding



  • I recently switched over to the unbound package to check it out and I noticed the following issues:

    1. I have "Enable registration of DHCP client names in DNS" enabled in my DHCP server settings. When a new client shows up on the network, unbound sometimes picks up on the new hostname (ie: it shows up in "Unbound local data", I can resolve the hostname, etc). Other times, no amount of reloading or prodding seems to cause the new hostname to show up.

    2. When forwarding is turned on, unbound only seems to want to forward the DNS servers designated by my ISP over DHCP on the WAN interface. If I specify different DNS servers in settings->general, no amount of reloading or enabling/disabling unbound seems to change what shows up in the "Unbound forwards" section of the "Unbound DNS status" tab.

    3. Occasionally, I find that unbound has simply stopped running. I suspect a config change elsewhere in pfSense triggers a failed reload, but I haven't noticed it right away, so I haven't managed to isolate what I did to cause it. Simply starting the service again from the pfSense services page doesn't usually work, but if I disable unbound, save, and then reenable unbound, it starts successfully. Sometimes when it manages to restart properly in this manner, new dhcp hostnames that didn't show up before (as described in #1) start showing up.

    Please let me know what I can do to help debug this. I'm fairly new to pfSense, so I'm still learning my way around.



  • For #2… try listing your pfSense box's IP under the DNS section on the DHCP Server config page, that's what sorted this out for me.
    This will tell your clients to use the pfSense box for DNS which in-turn will use Unbound. As I understand it, this won't always be necessary, but currently is.



  • @allan:

    I recently switched over to the unbound package to check it out and I noticed the following issues:

    1. I have "Enable registration of DHCP client names in DNS" enabled in my DHCP server settings. When a new client shows up on the network, unbound sometimes picks up on the new hostname (ie: it shows up in "Unbound local data", I can resolve the hostname, etc). Other times, no amount of reloading or prodding seems to cause the new hostname to show up.

    This is because Unbound needs to be saved if there are any new hostnames been added. This is not ideal but currently there is no way for Unbound to know if there are new changes.
    This will change with the integration of Unbound into 2.1.

    @allan:

    2. When forwarding is turned on, unbound only seems to want to forward the DNS servers designated by my ISP over DHCP on the WAN interface. If I specify different DNS servers in settings->general, no amount of reloading or enabling/disabling unbound seems to change what shows up in the "Unbound forwards" section of the "Unbound DNS status" tab.

    Do you have "Allow DNS server list to be overridden by DHCP/PPP on WAN" enabled?

    @allan:

    3. Occasionally, I find that unbound has simply stopped running. I suspect a config change elsewhere in pfSense triggers a failed reload, but I haven't noticed it right away, so I haven't managed to isolate what I did to cause it. Simply starting the service again from the pfSense services page doesn't usually work, but if I disable unbound, save, and then reenable unbound, it starts successfully. Sometimes when it manages to restart properly in this manner, new dhcp hostnames that didn't show up before (as described in #1) start showing up.

    This stopping might be related to a change which fixed another problem - Im still yet to find a fix for this.



  • @wagonza:

    This stopping might be related to a change which fixed another problem - Im still yet to find a fix for this.

    I have put a fix in for this, so just update your package.


Locked