DNS name resolution doesn't work on Artful
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
systemd (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
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/
On Ubuntu 17.04 this bug is not present.
The original address in /run/systemd/
It seems that the service systemd-networkd isn't active by default:
$ sudo systemctl status systemd-networkd
● systemd-
Loaded: loaded (/lib/systemd/
Active: inactive (dead)
Docs: man:systemd-
Manually starting it doesn't seem to help for this bug.
systemd-resolved is active:
$ sudo systemctl status systemd-resolved
● systemd-
Loaded: loaded (/lib/systemd/
Active: active (running) since Sat 2017-10-21 12:13:12 UTC; 44min ago
Docs: man:systemd-
https:/
https:/
https:/
Main PID: 1095 (systemd-resolve)
Status: "Processing requests..."
Tasks: 1 (limit: 4915)
CGroup: /system.
└─1095 /lib/systemd/
Okt 21 12:13:12 ubuntu systemd[1]: Starting Network Name Resolution...
Okt 21 12:13:12 ubuntu systemd-
Okt 21 12:13:12 ubuntu systemd-
Okt 21 12:13:12 ubuntu systemd-
Okt 21 12:13:12 ubuntu systemd-
Okt 21 12:13:12 ubuntu systemd-
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
ProcVersionSign
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/
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/
SourcePackage: systemd
SystemdDelta:
[EXTENDED] /lib/systemd/
[EXTENDED] /lib/systemd/
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.
dmi.modalias: dmi:bvnPhoenix:
dmi.product.name: Extensa 5635Z
dmi.product.
dmi.sys.vendor: Acer
I just tested that disabling systemd-resolved seems to be a good permanent workaround for me (according to the description under https:/ /askubuntu. com/questions/ 907246/ how-to- disable- systemd- resolved- in-ubuntu )