At least here it's because systemd-resolved insists on doing DNSSEC validation:
~$ sudo journalctl -u systemd-resolved | tail -5 Mar 27 13:30:55 ubuntu systemd-resolved[1083]: DNSSEC validation failed for question ubuntu.pool.ntp.org IN SOA: no-signature Mar 27 13:30:55 ubuntu systemd-resolved[1083]: DNSSEC validation failed for question 2.ubuntu.pool.ntp.org IN DS: no-signature Mar 27 13:30:55 ubuntu systemd-resolved[1083]: DNSSEC validation failed for question 2.ubuntu.pool.ntp.org IN SOA: no-signature Mar 27 13:30:55 ubuntu systemd-resolved[1083]: DNSSEC validation failed for question 2.ubuntu.pool.ntp.org IN A: no-signature Mar 27 13:30:55 ubuntu systemd-resolved[1083]: DNSSEC validation failed for question 2.ubuntu.pool.ntp.org IN AAAA: no-signature Hostnames with working DNSSEC records do work: ~$ getent hosts www.cloudflare.com 2400:cb00:2048:1::c629:d6a2 www.cloudflare.com 2400:cb00:2048:1::c629:d7a2 www.cloudflare.com -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1656830 Title: Ubuntu MATE 17.04: No DNS resolution caused by systemd-resolved To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1656830/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
