You are not logged in.
Pages: 1
I've got an issue where my network fails to resolve dns. It's find when I boot, then some apparently random time later, dns no longer works. When this occurs, it noticed that /etc/resolv.conf is empty. All my normal dns servers reported during dhcp lease are still accessible and work via ip address. If I add them back into resolv.conf dns works again. I did notice, that the last modified time of the resolv.conf appears to coincide with dhcpcd renewal, but there are no errors reported in journalctrl by /usr/bin/dhcpcd.
I didn't see anything in the forums about this when I searched. Anyone seen this before? Or have an idea how to trap whats erasing the file contents?
Thanks,
Jeremy
Offline
Maybe the problem lies with the dhcp server and it's sending an empty list upon renewal.
But whether the Constitution really be one thing, or another, this much is certain - that it has either authorized such a government as we have had, or has been powerless to prevent it. In either case, it is unfit to exist.
-Lysander Spooner
Offline
Pages: 1