https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=291790
--- Comment #2 from [email protected] --- > (In reply to Dag-Erling Smørgrav from comment #1) > FreeBSD has always required an /etc/resolv.conf. I don't know where you got > the idea that it didn't. [Foo, my previous reply seems to have been discarded. Trying again...] From: 1) (as I said in the description) the first line of /etc/resolv.conf.no which said: "#not when running name server on localhost; better to have no file" 2) the fact that my GENERIC system has been working just fine without an /etc/resolv.conf since at least as far back as 12.0-RELEASE-p1 in 2019, and 3) Upon looking into this further, I see the date on resolv.conf.no is April 25, 2012 (which is most likely the date I ceased having a resolv.conf), but it looks like I didn't switch to local-unbound until 2014, so I'm not sure what to think. What is clear is that, no, resolv.conf hasn't always been required for name resolution. I note that man resolv.conf still says: " On a normally configured system, setting this file manually should not be necessary. The only name server(s) to be queried will be on the local machine or automatically configured using DHCP or a similar mechanism, the domain name is determined from the host name, and the domain search path is constructed from the domain name. " which could be interpreted as either "file not required" or "the default file provided shouldn't need to be changed". Maybe that means it worked, but via a resolver other than the local named or unbound? No DHCP, though. I'm happy leaving this bug report closed. It's here if anyone else comes looking. -- You are receiving this mail because: You are the assignee for the bug.
