[Bug 1647031] Re: systemd-resolved’s 127.0.0.53 server does not follow CNAME records

[Barry Warsaw]

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
Foundations Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1647031

Title:
  systemd-resolved’s 127.0.0.53 server does not follow CNAME records

Status in systemd:
  New
Status in network-manager package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  $ systemd-resolve www.freedesktop.org
  www.freedesktop.org: 131.252.210.176
                       2610:10:20:722:a800:ff:feda:470f
                       (annarchy.freedesktop.org)

  -- Information acquired via protocol DNS in 673.6ms.
  -- Data is authenticated: no
  $ ping www.freedesktop.org
  ping: www.freedesktop.org: Name or service not known
  $ cat /etc/resolv.conf
  # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
  #     DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
  # 127.0.0.53 is the systemd-resolved stub resolver.
  # run "systemd-resolve --status" to see details about the actual nameservers.

  nameserver 127.0.0.53
  $ dig +no{cmd,comments,stats} www.freedesktop.org @127.0.0.53
  ;www.freedesktop.org.		IN	A
  www.freedesktop.org.	7146	IN	CNAME	annarchy.freedesktop.org.
  $ dig +no{cmd,comments,stats} www.freedesktop.org @8.8.8.8
  ;www.freedesktop.org.		IN	A
  www.freedesktop.org.	14399	IN	CNAME	annarchy.freedesktop.org.
  annarchy.freedesktop.org. 14399	IN	A	131.252.210.176

  I trust it needn’t be explained why this makes the internet almost
  completely useless in zesty.

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