Jan Komissar (jkomissa) wrote:
Hi Ernie,
1. Unbound does not use resolv.conf nor does it depend on your ISP name
servers. Instead it does its own DNS resolution by querying internet name
servers starting with the DNS root zone. Local zones are looked up before any
resolution happens.
2. If you must use your ISP name servers, you must configure a forward-zone
option for the root zone (.) pointing to them, and then you need to detect when
the ISP name server address(es) change(s) and use the unbound-control
forward_remove and forward_add commands to change the settings. (My ISPs have
rarely, if ever, changed their DNS server addresses, there is hardly ever a
reason to do that. I would just set up the forward-zone and handle DNS changes
manually, maybe write a script to translate resolv.conf nameservers to
unbound-control commands.)
HTH,
How do you tell unbound to go to this public root zone?
Is this root zone an unbound internal hard codded function?
