https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=291790
--- Comment #4 from [email protected] --- (In reply to Dag-Erling Smørgrav from comment #3) > 1. Your /etc/resolv.conf.no was not created or used by FreeBSD and we cannot > be held responsible for any (mis)information it contains. OK. If I wrote that line as a note to myself, it would have been because I saw it stated in pretty much those words somewhere, but as that was 2012, I've long since forgotten where. > 3. In the absence of /etc/resolv.conf, applications that rely on libc will > attempt to connect to a DNS server on INADDR_ANY and IN6ADDR_ANY. Whether or > not that succeeds depends on how your IP stack and your nameserver are > configured. Good to know, and you're agreeing yes, name resolution can work in the absence of /etc/resolv.conf. I also note that the man page for resolv.conf says that the resolver to use can also come from DHCP and other sources. > 4. In addition, libc will not attempt to use EDNS(0) unless explicitly told > to do so by /etc/resolv.conf, meaning that DNSSEC and anything that relies on > it (like SSHFP records) will most likely not work. Haven't tried to use that, so I make no claim that that used to work. > The only way to ensure consistent and reliable operation is to provide an > /etc/resolv.conf that everyone understands. Sounds good, and now I've got one. If anyone else runs into this problem, point them to this page. -- You are receiving this mail because: You are the assignee for the bug.
