Interesting. It worked and works for me. I tested the version in my PPA, both outside and inside a chroot (it was the inside-chroot that was previously broken). I just dist-upgraded my other Zesty machine and rebooted, and I am having no troubles resolving both IP and domain names both on my LAN and in the wider internet (www.ubuntu.com, www.python.org, youtube.com). The output of `systemd-resolve --status` LGTM, with my bridge0 link getting the correct DNS server (local to my LAN) and DNS domain.
chroots also look good (previously they could not get to my apt-cache-ng proxy on my LAN). Virtual machines on the same host are also working fine afaict. Since two of you have reported problems so closely together, there must be Something Going On, but I cannot reproduce it. Can you please review your Network Connections from the network manager settings panel? Is there anything weird, misconfigured, or unexpected there? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1647031 Title: systemd-resolved’s 127.0.0.53 server does not follow CNAME records To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1647031/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
