Note that on my machine (clean 16.10 install, upgraded to 17.04 and
later 17.10), DNS resolution already partially broke in 17.04 (involving
the switch to systemd-resolve). With Ubuntu 17.04, DNS resolution was
broken after suspending, moving to a different WiFi, and resuming the
machine. This could be manually fixed by manually running dhclient.
This does not fix the abovementioned issue, though.
** Description changed:
Since upgrading to 17.10, hostname resolution (via, e.g., Firefox or the
"host" command-line tool) does not work reliably anymore. Once hostname
resolution fails (Firefox 57: "Hmm. We're having trouble finding that
site."), manually resolving the host via "systemd-resolve" succeeds and
temporarily allows Firefox to also resolve that host. After a few
minutes, resolution of the same host fails again.
Example with command-line "host" utility:
$ host www.heise.de
;; connection timed out; no servers could be reached
- $ cat /etc/resolv.conf
+ $ 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
search fritz.box
$ systemd-resolve www.heise.de
www.heise.de: 2a02:2e0:3fe:1001::772e:2:85
- 193.99.144.85
+ 193.99.144.85
-- Information acquired via protocol DNS in 273.2ms.
-- Data is authenticated: no
$ host www.heise.de
www.heise.de has address 193.99.144.85
www.heise.de has IPv6 address 2a02:2e0:3fe:1001::772e:2:85
+ $ systemd-resolve --status
Global
- DNS Servers: 192.168.178.1
- DNS Domain: fritz.box
- DNSSEC NTA: 10.in-addr.arpa
- 16.172.in-addr.arpa
- 168.192.in-addr.arpa
- 17.172.in-addr.arpa
- 18.172.in-addr.arpa
- 19.172.in-addr.arpa
- 20.172.in-addr.arpa
- 21.172.in-addr.arpa
- 22.172.in-addr.arpa
- 23.172.in-addr.arpa
- 24.172.in-addr.arpa
- 25.172.in-addr.arpa
- 26.172.in-addr.arpa
- 27.172.in-addr.arpa
- 28.172.in-addr.arpa
- 29.172.in-addr.arpa
- 30.172.in-addr.arpa
- 31.172.in-addr.arpa
- corp
- d.f.ip6.arpa
- home
- internal
- intranet
- lan
- local
- private
- test
+ DNS Servers: 192.168.178.1
+ DNS Domain: fritz.box
+ DNSSEC NTA: 10.in-addr.arpa
+ 16.172.in-addr.arpa
+ 168.192.in-addr.arpa
+ 17.172.in-addr.arpa
+ 18.172.in-addr.arpa
+ 19.172.in-addr.arpa
+ 20.172.in-addr.arpa
+ 21.172.in-addr.arpa
+ 22.172.in-addr.arpa
+ 23.172.in-addr.arpa
+ 24.172.in-addr.arpa
+ 25.172.in-addr.arpa
+ 26.172.in-addr.arpa
+ 27.172.in-addr.arpa
+ 28.172.in-addr.arpa
+ 29.172.in-addr.arpa
+ 30.172.in-addr.arpa
+ 31.172.in-addr.arpa
+ corp
+ d.f.ip6.arpa
+ home
+ internal
+ intranet
+ lan
+ local
+ private
+ test
Link 4 (wlp3s0)
- Current Scopes: DNS LLMNR/IPv4 LLMNR/IPv6
-LLMNR setting: yes
+ Current Scopes: DNS LLMNR/IPv4 LLMNR/IPv6
+ LLMNR setting: yes
MulticastDNS setting: no
- DNSSEC setting: no
- DNSSEC supported: no
- DNS Servers: fd00::cece:1eff:fe61:2ece
+ DNSSEC setting: no
+ DNSSEC supported: no
+ DNS Servers: fd00::cece:1eff:fe61:2ece
Link 3 (enp0s20f0u5c2)
- Current Scopes: none
-LLMNR setting: yes
+ Current Scopes: none
+ LLMNR setting: yes
MulticastDNS setting: no
- DNSSEC setting: no
- DNSSEC supported: no
+ DNSSEC setting: no
+ DNSSEC supported: no
Link 2 (enp0s31f6)
- Current Scopes: none
-LLMNR setting: yes
+ Current Scopes: none
+ LLMNR setting: yes
MulticastDNS setting: no
- DNSSEC setting: no
- DNSSEC supported: no
+ DNSSEC setting: no
+ DNSSEC supported:
