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
