Bug 286090 - resolvconf.conf gets ignored when using a DHCP client
Summary: resolvconf.conf gets ignored when using a DHCP client
Status: New
Alias: None
Product: Base System
Classification: Unclassified
Component: conf (show other bugs)
Version: 14.2-STABLE
Hardware: Any Any
: --- Affects Many People
Assignee: freebsd-bugs (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-04-14 12:09 UTC by Daniel Ziltener
Modified: 2025-04-22 20:15 UTC (History)
2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Daniel Ziltener 2025-04-14 12:09:18 UTC 
I'm on a system with dual-dhclient-daemon, but it seems to also happen with the standard dclient. My /etc/resolvconf.conf gets completely ignored.

First, I tried setting additional nameservers in there using the "name_servers" and "name_servers_append" config options. They did not get added after a reboot.

I tried manually putting my nameservers into /etc/resolv.conf and putting "resolvconf=NO" into /etc/resolvconf.conf. Again, this had no effect, the resolv.conf got overwritten.

Ultimately, I added resolv_conf=/dev/null, but again, this got ignored and the resolv.conf overwritten.

My workaround is to overwrite resolv.conf in my rc.local, but that's not a solution.