[Bug 1737732] Re: systemd-resolve default nameserver 127.0.0.53 disables resolution in guest systems

[Steve Langasek]

I can't reproduce this issue.  Can you explain what I'm missing?

$ grep nameserver /etc/resolv.conf 
# run "systemd-resolve --status" to see details about the actual nameservers.
nameserver 127.0.0.53
$ lxc launch ubuntu-daily:bionic
Creating the container
Container name is: frank-jaguar               
Starting frank-jaguar
$ lxc exec frank-jaguar -- ping -c 1 www.google.com
PING www.google.com (74.125.199.105) 56(84) bytes of data.
64 bytes from ph-in-f105.1e100.net (74.125.199.105): icmp_seq=1 ttl=46 time=30.3 ms

--- www.google.com ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 30.326/30.326/30.326/0.000 ms
$

So can you elaborate where you're seeing this problem?

** Changed in: systemd (Ubuntu)
       Status: New => Incomplete

-- 
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/1737732

Title:
  systemd-resolve default nameserver 127.0.0.53 disables resolution in
  guest systems

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  When the default nameserver, which is set by systemd-resolve, is
  127.0.0.53, guest systems (libvirtd, lxc, snaps, anbox, etc) won't
  work unless there's a non 127.0.0.x nameserver (eg. 8.8.8.8) in
  /etc/resolv.conf.  Because the dnsmasq in these guest machines try to
  resolve to 127.0.0.53 and can't find the real nameserver.

  The quick fix is of course to:

  sudo rm /etc/resolv.conf
  sudo ln -s /run/systemd/resolve/resolv.conf /etc/resolv.conf

  But that's not the default.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: systemd 234-2ubuntu12.2
  ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13
  Uname: Linux 4.13.0-19-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Dec 12 20:01:39 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-09-28 (805 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: LENOVO 34361A0
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-19-generic root=UUID=da81a856-84d5-4ca7-8c0a-4f20006730bc ro quiet splash nomodset vga=792 vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/24/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GCETA3WW (2.63 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 34361A0
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: dmi:bvnLENOVO:bvrGCETA3WW(2.63):bd09/24/2015:svnLENOVO:pn34361A0:pvrThinkPadX220:rvnLENOVO:rn34361A0:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad X220
  dmi.product.name: 34361A0
  dmi.product.version: ThinkPad X220
  dmi.sys.vendor: LENOVO
  mtime.conffile..etc.systemd.journald.conf: 2017-09-12T19:43:29.248459

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