[Bug 1710410] [NEW] Must run systemd-resolve --status before DNS resolving is operative
WoJ
1710410 at bugs.launchpad.net
Sat Aug 12 19:45:53 UTC 2017
Public bug reported:
Context: fresh install of zesty via
debootstrap --include=nano,dbus,iputils-ping,iproute2 zesty zesty1
http://fr.archive.ubuntu.com/ubuntu
ran via asystemd-nspawn with a static IP
1. Upon first connexion, a ping fails:
root at zesty1:~# ping google.com
ping: google.com: Temporary failure in name resolution
2. The content of /etc/resolv.conf:
root at zesty1:~# 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.
3. When running systemd-resolve --status:
root at zesty1:~# systemd-resolve --status
Global
DNS Servers: 8.8.8.8
8.8.4.4
2001:4860:4860::8888
2001:4860:4860::8844
DNSSEC NTA: 10.in-addr.arpa
16.172.in-addr.arpa
168.192.in-addr.arpa
(...)
4. After running this command the resolution is miraculously restored:
root at zesty1:~# ping google.com
PING google.com (172.217.22.142) 56(84) bytes of data.
64 bytes from 172.217.22.142 (172.217.22.142): icmp_seq=1 ttl=53 time=2.62 ms
64 bytes from 172.217.22.142 (172.217.22.142): icmp_seq=2 ttl=53 time=1.93 ms
** Affects: systemd (Ubuntu)
Importance: Undecided
Status: New
--
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/1710410
Title:
Must run systemd-resolve --status before DNS resolving is operative
Status in systemd package in Ubuntu:
New
Bug description:
Context: fresh install of zesty via
debootstrap --include=nano,dbus,iputils-ping,iproute2 zesty zesty1
http://fr.archive.ubuntu.com/ubuntu
ran via asystemd-nspawn with a static IP
1. Upon first connexion, a ping fails:
root at zesty1:~# ping google.com
ping: google.com: Temporary failure in name resolution
2. The content of /etc/resolv.conf:
root at zesty1:~# 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.
3. When running systemd-resolve --status:
root at zesty1:~# systemd-resolve --status
Global
DNS Servers: 8.8.8.8
8.8.4.4
2001:4860:4860::8888
2001:4860:4860::8844
DNSSEC NTA: 10.in-addr.arpa
16.172.in-addr.arpa
168.192.in-addr.arpa
(...)
4. After running this command the resolution is miraculously restored:
root at zesty1:~# ping google.com
PING google.com (172.217.22.142) 56(84) bytes of data.
64 bytes from 172.217.22.142 (172.217.22.142): icmp_seq=1 ttl=53 time=2.62 ms
64 bytes from 172.217.22.142 (172.217.22.142): icmp_seq=2 ttl=53 time=1.93 ms
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1710410/+subscriptions
More information about the foundations-bugs
mailing list