systemd-resolved forgets to use local DNS

[fivemack]

About every other day, my ubuntu-18.04 machines forget that I have a local DNS server. I can get them to remember by restarting systemd-resolved, but does anyone know where that service keeps its logs and why it might forget about the local DNS server (which is advertised on dhcp4 and dhcp6) occasionally?

pineapple@pineapple:~$ ssh oak@oak
ssh: Could not resolve hostname oak: Temporary failure in name resolution
pineapple@pineapple:~$ sudo systemctl restart systemd-resolved.service
[sudo] password for pineapple:

[paulunderwood]

Originally Posted by fivemack

About every other day, my ubuntu-18.04 machines forget that I have a local DNS server. I can get them to remember by restarting systemd-resolved, but does anyone know where that service keeps its logs and why it might forget about the local DNS server (which is advertised on dhcp4 and dhcp6) occasionally?

pineapple@pineapple:~$ ssh oak@oak
ssh: Could not resolve hostname oak: Temporary failure in name resolution
pineapple@pineapple:~$ sudo systemctl restart systemd-resolved.service
[sudo] password for pineapple:

I don't know where it will be logged, maybe /var/log/, but have you tried sudo systemctl enable systemd-resolved.service ? Alternatively you could use a local /etc/hosts file.

[ric]

Originally Posted by fivemack

does anyone know where that service keeps its logs and why it might forget about the local DNS server (which is advertised on dhcp4 and dhcp6) occasionally?

As per this post (2nd answer), you may want to use

journalctl -u systemd-resolved -f

and follow the suggestion within that post to elevate loglevel by editing systemd-resolved, for some clues.
HTH

<RANT on systemd></RANT> ;-)

[Mark Rose]

https://askubuntu.com/questions/9072...lved-in-ubuntu