I've been having issues with name resolution after an update from 18.04 to 18.10 threw off some of my network settings.
After tracing the issue around, I found that if I write nameserver 8.8.8.8 directly to /etc/resolv.conf, it resolves the issue until next bootup. The problem is that I can't figure out what service/setting is overwriting resolv.conf back to 127.0.0.1
- I've checked /etc/resolvconf/resolv.conf.d/base, but I already have nameserver 8.8.8.8 entered in there.
- The header in resolv.conf mentions changes should be made related to systemd-resolve, but I receive the error: Failed to get global data: Unit dbus-org.freedesktop.resolve1.service not found.
As a further note, I am running PiHole, which is basically a wrapper for dnsmasq which pulls lists of known bad IP addresses (ads, spam, etc) and blocks them from name resolution. It works as your network's DNS server and thus allows you to configure forward DNS query addresses. (You can configure multiple and it will choose the fastest). This MAY be overriding or conflicting with another process that is normally disabled by pihole, but re-enabled during the update. My next step there is to try reinstalling PiHole to see if it configures things back.
Do you guys know a way to figure out what is currently sourcing my list of nameservers? (Or for that matter, a way to clean up redundant junk from other services and files trying to perform the same task?)
After tracing the issue around, I found that if I write nameserver 8.8.8.8 directly to /etc/resolv.conf, it resolves the issue until next bootup. The problem is that I can't figure out what service/setting is overwriting resolv.conf back to 127.0.0.1
- I've checked /etc/resolvconf/resolv.conf.d/base, but I already have nameserver 8.8.8.8 entered in there.
- The header in resolv.conf mentions changes should be made related to systemd-resolve, but I receive the error: Failed to get global data: Unit dbus-org.freedesktop.resolve1.service not found.
As a further note, I am running PiHole, which is basically a wrapper for dnsmasq which pulls lists of known bad IP addresses (ads, spam, etc) and blocks them from name resolution. It works as your network's DNS server and thus allows you to configure forward DNS query addresses. (You can configure multiple and it will choose the fastest). This MAY be overriding or conflicting with another process that is normally disabled by pihole, but re-enabled during the update. My next step there is to try reinstalling PiHole to see if it configures things back.
Do you guys know a way to figure out what is currently sourcing my list of nameservers? (Or for that matter, a way to clean up redundant junk from other services and files trying to perform the same task?)