[arch-general] /etc/resolv.conf continuously wiped since yesterday
since a reboot/updates yesterday my /etc/resolv.conf has been getting wiped (when it happens I lose all dns). I don't know why. does anyone have any ideas what might be going on? # A sample configuration for dhcpcd. # See dhcpcd.conf(5) for details. # Inform the DHCP server of our hostname for DDNS. hostname # A list of options to request from the DHCP server. # Most distributions have NTP support. option ntp_servers # Behave nicely on networks and respect their MTU. # However, a lot of buggy DHCP servers set invalid MTUs so this is not # enabled by default. #option interface_mtu # A ServerID is required by RFC2131. # Some broken DHCP servers do not send one and dhcpcd can work without it. # Some broken DHCP servers NAK incorrectly and do not include a ServerID either so # the default is to require a ServerID. require dhcp_server_identifier # A hook script is provided to lookup the hostname if not set by the DHCP # server, but it should not be run by default. nohook lookup-hostname noipv4ll -- Caleb Cushing http://xenoterracide.blogspot.com
IIRC, resolv.conf is supposed to get automatically overwritten by your DHCP client, as a result of the new DHCP & DNS info it receives when it initiates a network connection. So the question isn't "why is it getting overwritten", but rather "why is it getting overwritten with incorrect values that are making my DNS lookups fail". Try performing an nslookup on some site and see which DNS servers your system is getting configured to use. Once you know which servers your system is using, you can then try to figure out why the DNS lookups are failing. HTH, DR Caleb Cushing wrote:
since a reboot/updates yesterday my /etc/resolv.conf has been getting wiped (when it happens I lose all dns). I don't know why. does anyone have any ideas what might be going on?
# A sample configuration for dhcpcd. # See dhcpcd.conf(5) for details.
# Inform the DHCP server of our hostname for DDNS. hostname
# A list of options to request from the DHCP server. # Most distributions have NTP support. option ntp_servers
# Behave nicely on networks and respect their MTU. # However, a lot of buggy DHCP servers set invalid MTUs so this is not # enabled by default. #option interface_mtu
# A ServerID is required by RFC2131. # Some broken DHCP servers do not send one and dhcpcd can work without it. # Some broken DHCP servers NAK incorrectly and do not include a ServerID either so # the default is to require a ServerID. require dhcp_server_identifier
# A hook script is provided to lookup the hostname if not set by the DHCP # server, but it should not be run by default. nohook lookup-hostname noipv4ll
On Fri, Jul 10, 2009 at 11:00 AM, David Rosenstrauch
IIRC, resolv.conf is supposed to get automatically overwritten by your DHCP client, as a result of the new DHCP & DNS info it receives when it initiates a network connection.
This is correct. There should be .head and .tail files you can add which are automatically merged (check the docs). But more to the point - why are you putting values from dhcpcd.conf into resolv.conf?
On Fri, Jul 10, 2009 at 12:08 PM, Aaron Griffin
This is correct. There should be .head and .tail files you can add which are automatically merged (check the docs). But more to the point - why are you putting values from dhcpcd.conf into resolv.conf?
I was showing you how dhcpcd.conf is configured. that's not resolv.conf. resolv.conf just ends up with this. # Generated by dhcpcd # /etc/resolv.conf.head can replace this line # /etc/resolv.conf.tail can replace this line again I didn't have this problem until today after I rebooted my system. and I haven't changed my configuration at all. -- Caleb Cushing http://xenoterracide.blogspot.com
So the question isn't "why is it getting overwritten", but rather "why is it getting overwritten with incorrect values that are making my DNS lookups fail".
Try performing an nslookup on some site and see which DNS servers your system is getting configured to use. Once you know which servers your system is using, you can then try to figure out why the DNS lookups are failing.
the problem is it's ending up with no values. -- Caleb Cushing http://xenoterracide.blogspot.com
Caleb Cushing wrote:
So the question isn't "why is it getting overwritten", but rather "why is it getting overwritten with incorrect values that are making my DNS lookups fail".
Try performing an nslookup on some site and see which DNS servers your system is getting configured to use. Once you know which servers your system is using, you can then try to figure out why the DNS lookups are failing.
the problem is it's ending up with no values.
Are you sure then your dhcp client is succeeding? i.e., is it crashing somewhere? From the command line try killing any existing dhcp client, and then running it again from the command line. Should give you something more of a clue I'd think. It'd be surprising to me if the dhcp client were successful and yet still not populate your resolve.conf. HTH, DR
On Fri-2009/07/10-21:53 Caleb Cushing wrote:
the problem is it's ending up with no values.
If you prefer to have your own settings in etc/resolv.conf, you can do this: create "/etc/dhcpcd.enter-hook" with example contents: # what is supposed to be in /etc/resolv.conf: new_domain_name="." new_domain_name_servers="127.0.0.53" exit_status=0 clemens
participants (4)
-
Aaron Griffin
-
Caleb Cushing
-
clemens fischer
-
David Rosenstrauch