[Bug 1725680] Re: DNS name resolution doesn't work on Artful

[Jan Rathmann]

@Sebastien
Well, hmmm, it is possible that #1727237 is the same bug. The wifi I was using at that time was a bit weird in regards of having a captive portal: It seemed to me that it was implemented to show a captive portal in principle when connecting to it. But while some other people around were directed to that captive portal everytime they connected to the wifi, I saw it on my devices (Android phone and the laptop where I send this report from) only at the first connection - then I regularily connected to this wifi for months(!) and the captive portal was never shown again to me! And that's the reason why I even forgot to metion it at all in this bug report.

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

Title:
  DNS name resolution doesn't work on Artful

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  If I boot my laptop with a live image or an installation of Ubuntu
  17.10, DNS name resolution doesn't work (which means I can't access
  any website).

  Steps to reproduce:
  - Boot laptop with Ubuntu 17.10 live image
  - Connect to my wireless network
  - Try to ping any website, e.g. ping ubuntu.com. This immediately fails with the error message "Name or service not known"
  - Try to ping an IP-adress, e.g. ping 8.8.8.8 : this works.

  As a workaround, I can get a temporarily working DNS resolution by
  manually editing /etc/resolv.conf (symlink to /run/systemd/resolve
  /stub-resolve.conf) and setting the "nameserver" entry to 8.8.8.8 or
  some other known DNS server.

  On Ubuntu 17.04 this bug is not present.

  The original address in /run/systemd/resolve/stub-resolve.conf is
  127.0.0.53 . I get immediate replies if I ping this address, but
  nevertheless DNS resolution doesn't work.

  It seems that the service systemd-networkd isn't active by default:
  $ sudo systemctl status systemd-networkd
  ● systemd-networkd.service - Network Service
     Loaded: loaded (/lib/systemd/system/systemd-networkd.service; disabled; vendo
     Active: inactive (dead)
       Docs: man:systemd-networkd.service(8)

  Manually starting it doesn't seem to help for this bug.

  systemd-resolved is active:

  $ sudo systemctl status systemd-resolved
  ● systemd-resolved.service - Network Name Resolution
     Loaded: loaded (/lib/systemd/system/systemd-resolved.service; enabled; vendor
     Active: active (running) since Sat 2017-10-21 12:13:12 UTC; 44min ago
       Docs: man:systemd-resolved.service(8)
             https://www.freedesktop.org/wiki/Software/systemd/resolved
             https://www.freedesktop.org/wiki/Software/systemd/writing-network-con
             https://www.freedesktop.org/wiki/Software/systemd/writing-resolver-cl
   Main PID: 1095 (systemd-resolve)
     Status: "Processing requests..."
      Tasks: 1 (limit: 4915)
     CGroup: /system.slice/systemd-resolved.service
             └─1095 /lib/systemd/systemd-resolved

  Okt 21 12:13:12 ubuntu systemd[1]: Starting Network Name Resolution...
  Okt 21 12:13:12 ubuntu systemd-resolved[1095]: Positive Trust Anchors:
  Okt 21 12:13:12 ubuntu systemd-resolved[1095]: . IN DS 19036 8 2 49aac11d7b6f644
  Okt 21 12:13:12 ubuntu systemd-resolved[1095]: . IN DS 20326 8 2 e06d44b80b8f1d3
  Okt 21 12:13:12 ubuntu systemd-resolved[1095]: Negative trust anchors: 10.in-add
  Okt 21 12:13:12 ubuntu systemd-resolved[1095]: Using system hostname 'ubuntu'.
  Okt 21 12:13:12 ubuntu systemd[1]: Started Network Name Resolution.

  Kind regards,
  Jan

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: systemd 234-2ubuntu12
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CasperVersion: 1.387
  Date: Sat Oct 21 12:26:00 2017
  ExecutablePath: /lib/systemd/systemd-resolved
  LiveMediaBuild: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: Acer Extensa 5635Z
  ProcEnviron:
   LANG=C.UTF-8
   PATH=(custom, no user)
  ProcKernelCmdLine: file=/cdrom/preseed/hostname.seed boot=casper initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/user at .service → /lib/systemd/system/user at .service.d/timeout.conf
   
   2 overridden configuration files found.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/14/2009
  dmi.bios.vendor: Phoenix
  dmi.bios.version: V0.3305
  dmi.board.name: BA50-MV
  dmi.board.vendor: Acer
  dmi.board.version: Not Applicable
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: N/A
  dmi.modalias: dmi:bvnPhoenix:bvrV0.3305:bd08/14/2009:svnAcer:pnExtensa5635Z:pvrNotApplicable:rvnAcer:rnBA50-MV:rvrNotApplicable:cvnAcer:ct10:cvrN/A:
  dmi.product.name: Extensa 5635Z
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Acer

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