On 2022-04-19 13:22:53 +0300, Michael Tokarev wrote: > In my understanding over the years, I expected the nameservers > received from/by DHCP should be used *first*. I did this with > unbound or dnsmasq even before resolvconf has been written - > using custom dhcp script to reconfigure local DNS resolver. > > I don't even know unbund has a way to specify "fallback" > nameservers. You either set forwarders for a zone or you don't, > there's no _notion_ of fallback per se.
The fallback is what resolvconf expects and precisely why bug 1003135 was reassigned from resolvconf to unbound: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003135#40 "In fact, unbound comes with resolvconf integration, so it should know about other nameservers coming from DHCP. [...]" Note: resolvconf filters out nameservers coming from DHCP only those that are placed after 127.0.0.1, i.e. those that are normally used as a fallback when resolvconf isn't installed, because it assumes that this fallback is provided by the local nameserver (here, unbound). -- Vincent Lefèvre <vinc...@vinc17.net> - Web: <https://www.vinc17.net/> 100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/> Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)
