[Bug 1658592] [NEW] systemd-resolved causing google.com not reachable

[John]

Public bug reported:

System info:
lsb_release -rd: Description:	Ubuntu Zesty Zapus (development branch)
Release:	17.04

uname -a:
Linux pc 4.9.0-12-generic #13-Ubuntu SMP Mon Jan 9 20:06:25 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

systemd --version:
systemd 232
+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD +IDN

Static IP address(10.0.0.250/16), DNS(8.8.8.8) and routes(10.0.0.1) are
set manually in network manager.

Problem Description:

1. google.com is not accessible from firefox or chromium, but
google.co.uk, google.co.jp can be accessble. Firefox would redirect
google.com to
"https://www.google.com.sg/?gfe_rd=cr&ei=eaCFWLfUDIe1vASXoY7gBA" reports
an error "Firefox can’t find the server at www.google.com.sg." Chromium
redirect to google.com.sg too and reports a DNS error.

2. ping and host google.com shows no errors and reports correct IP
addresses.

3. ping: google.com.sg: Name or service not known

4. host google.com.sg: google.com.sg has address 74.125.130.94

5. entering 74.125.130.94 directly in Firefox address bar redirect the
webpage to
"https://www.google.com.sg/?gfe_rd=cr&ei=paKFWO2sJ9LFuASvwq2ADA"

6. other PC running fedora distro in the same lan can reach google.com
with firefox or chromium.

7. Looking at /etc/resolve.conf, nameserver is 127.0.0.53. It also
suggests systemd-resolved.service is in charge of name resolution. If I
stop this service and change nameserver in /etc/resolv.conf to 8.8.8.8,
`google.com` can be accessed from firefox.

8. If changing nameserver back to 127.0.0.53 and start systemd-
resolved.service, google.com is not accessible from browser anymore.

The above step seems to suggest the problem is with systemd-
resolved.service.

** Affects: systemd (Ubuntu)
     Importance: Undecided
         Status: New


** Tags: google systemd-resolved

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1658592

Title:
  systemd-resolved causing google.com not reachable

Status in systemd package in Ubuntu:
  New

Bug description:
  System info:
  lsb_release -rd: Description:	Ubuntu Zesty Zapus (development branch)
  Release:	17.04

  uname -a:
  Linux pc 4.9.0-12-generic #13-Ubuntu SMP Mon Jan 9 20:06:25 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

  systemd --version:
  systemd 232
  +PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD +IDN

  Static IP address(10.0.0.250/16), DNS(8.8.8.8) and routes(10.0.0.1)
  are set manually in network manager.

  Problem Description:

  1. google.com is not accessible from firefox or chromium, but
  google.co.uk, google.co.jp can be accessble. Firefox would redirect
  google.com to
  "https://www.google.com.sg/?gfe_rd=cr&ei=eaCFWLfUDIe1vASXoY7gBA"
  reports an error "Firefox can’t find the server at www.google.com.sg."
  Chromium redirect to google.com.sg too and reports a DNS error.

  2. ping and host google.com shows no errors and reports correct IP
  addresses.

  3. ping: google.com.sg: Name or service not known

  4. host google.com.sg: google.com.sg has address 74.125.130.94

  5. entering 74.125.130.94 directly in Firefox address bar redirect the
  webpage to
  "https://www.google.com.sg/?gfe_rd=cr&ei=paKFWO2sJ9LFuASvwq2ADA"

  6. other PC running fedora distro in the same lan can reach google.com
  with firefox or chromium.

  7. Looking at /etc/resolve.conf, nameserver is 127.0.0.53. It also
  suggests systemd-resolved.service is in charge of name resolution. If
  I stop this service and change nameserver in /etc/resolv.conf to
  8.8.8.8, `google.com` can be accessed from firefox.

  8. If changing nameserver back to 127.0.0.53 and start systemd-
  resolved.service, google.com is not accessible from browser anymore.

  The above step seems to suggest the problem is with systemd-
  resolved.service.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1658592/+subscriptions