[Bug 1729194] Re: Systemd-Resolvd Forgets to Resolv Request

2018-01-26 Thread Steve Langasek
127.0.1.1 is not the address of systemd-resolved, as you noted; it's the address used by dnsmasq. It sounds like your network-manager config is pointing to dnsmasq, which is no longer the default in 17.10, and should have been dropped from your config on upgrade from 16.10 to 17.04. Can you pleas

[Bug 1729194] Re: Systemd-Resolvd Forgets to Resolv Request

2017-12-29 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: systemd (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1729194 Title: Sy

[Bug 1729194] Re: Systemd-Resolvd Forgets to Resolv Request

2017-11-01 Thread Christopher
Some more troubleshooting, I've found that if I manually set my nameserver to 127.0.0.53 systemd-resolver starts working again. However everytime that a wifi network connects or disconnects, it switches back to `127.0.0.1` It does look like systemd-resolve only listens on that port too. : `udp