You may also use dig, to discover and check things by-passing resolved. E.g. $ dig google.com.sg @8.8.8.8
Note that 8.8.8.8 is globally distributed DNS using anycast routing, meaning the results from 8.8.8.8 that I see, may not be the results you see. google.com.sg looks ok for me, and google.com too. However, the redirect from google.com -> google.com.sg is location dependant. If you hit, this or similar problem in the future, it would be helpful to attach output of $ systemd-resolve --status As that shows what upstream DNS servers resolved is using. Most of the time, using 8.8.8.8 is the wrong answer, and you should, ideally, use your internal workplace and/or ISP DNS =) Furthermore '$ journalctl -b -e -u systemd-resolved' may show warnings and errors from DNS resolutions. $ systemd-resolve --flush-caches $ systemd-resolve --reset-server-features Are also useful debugging tools, to flush resolved state - drop cached responses, and revert to trying DNS requests with highest feature set (e.g. with EDNS0 / dnssec / etc). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1658592 Title: systemd-resolved causing google.com not reachable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1658592/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
