Date: Thu, 18 Dec 2025 23:07:27 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 291790] local-unbound: /etc/resolv.conf needed by 15.0, not wanted in 14.3, not created by upgrade Message-ID: <bug-291790-227@https.bugs.freebsd.org/bugzilla/>
index | next in thread | raw e-mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=291790 Bug ID: 291790 Summary: local-unbound: /etc/resolv.conf needed by 15.0, not wanted in 14.3, not created by upgrade Product: Base System Version: 15.0-RELEASE Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: bin Assignee: bugs@FreeBSD.org Reporter: wbe@psr.com This appears to be an "upgrade from 14.3 to 15.0" issue. In 14.3-RELEASE-p7 (actually pretty much any 14.*), local-unbound did not need /etc/resolv.conf. Indeed, the file /etc/resolv.conf.no specifically says: "#not when running name server on localhost; better to have no file" However, in 15.0-RELEASE-p1, I find that /etc/resolv.conf needs to exist. Indeed, 15.0's "man local-unbound" says: "To use a locally running Unbound for resolving put nameserver 127.0.0.1 into resolv.conf(5)." In 15.0 without /etc/resolv.conf, name resolution fails. When upgrading from 14.3 (which didn't have resolv.conf and worked fine) to 15.0 (which needs it to work), the file was not created. The first symptom I encountered during the upgrade, however, was something else entirely: "pkg upgrade -f" (and even just "pkg update") didn't work. It took me a while to figure out what the actual problem was (i.e., not pkg or its configuration). [More on that in a separate bug report I'll submit next.] Creating /etc/resolv.conf made things work again. I see this as a 1-time transition to 15.0 issue. Submitting this documents the problem. -- You are receiving this mail because: You are the assignee for the bug.home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-291790-227>