After upgrading from Cosmic, which works as expected, and rebooting, I am unable to do any network name resolution. Pinging and connecting with firefox via ip address works fine, but name lookups do not. nslookup just sits there and eventually times out. I have tried stopping and restarting systemd-resolved.service and resolvconf-pull-resolved.service, with no effect. Now here is the really strange part: if I wait 5-10 minutes, then the miserable thing starts working!! I have no idea why, or what is kicking in.
The only thing I have been able to pin down is this: if I do a
systemctl status systemd-resolved.service
both before and after it works, I get the following:
Not-working:
And working:
diff says the difference between the two, other than times and memory locations, is the last line, present in the "working" status:
Apr 28 14:50:13 Crynfyd systemd-resolved[1010]: Using degraded feature set (UDP) for DNS server 192.168.1.1.
Well this is bizarre. I don't know why it should start working several minutes after bootup.
PS I should mention two things: During the upgrade, somehow most of kde got whacked. I reinstalled kubuntu-desktop, and all SEEMS well, but maybe not. Also, the network problem exists both from the console and from inside kde.
The only thing I have been able to pin down is this: if I do a
systemctl status systemd-resolved.service
both before and after it works, I get the following:
Not-working:
Code:
greenman@Crynfyd19.04 ~$ cat not-working ● systemd-resolved.service - Network Name Resolution Loaded: loaded (/lib/systemd/system/systemd-resolved.service; enabled; vendor preset: enabled) Active: active (running) since Sun 2019-04-28 14:44:21 PDT; 3min 24s ago Docs: man:systemd-resolved.service(8) https://www.freedesktop.org/wiki/Software/systemd/resolved https://www.freedesktop.org/wiki/Software/systemd/writing-network-configuration-managers https://www.freedesktop.org/wiki/Software/systemd/writing-resolver-clients Main PID: 1010 (systemd-resolve) Status: "Processing requests..." Tasks: 1 (limit: 4915) Memory: 4.0M CGroup: /system.slice/systemd-resolved.service └─1010 /lib/systemd/systemd-resolved Apr 28 14:44:10 Crynfyd systemd[1]: Starting Network Name Resolution... Apr 28 14:44:14 Crynfyd systemd-resolved[1010]: Positive Trust Anchors: Apr 28 14:44:14 Crynfyd systemd-resolved[1010]: . IN DS 19036 8 2 49aac11d7b6f6446702e54a1607371607a1a41855200fd2ce1cdde32f24e8fb5 Apr 28 14:44:14 Crynfyd systemd-resolved[1010]: . IN DS 20326 8 2 e06d44b80b8f1d39a95c0b0d7c65d08458e880409bbc683457104237c7f8ec8d Apr 28 14:44:14 Crynfyd systemd-resolved[1010]: Negative trust anchors: 10.in-addr.arpa 16.172.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 168.192.in-addr.arpa d.f.ip6.arpa corp home internal intranet lan local private test Apr 28 14:44:14 Crynfyd systemd-resolved[1010]: Using system hostname 'Crynfyd'. Apr 28 14:44:21 Crynfyd systemd[1]: Started Network Name Resolution.
Code:
greenman@Crynfyd19.04 ~$ cat working ● systemd-resolved.service - Network Name Resolution Loaded: loaded (/lib/systemd/system/systemd-resolved.service; enabled; vendor preset: enabled) Active: active (running) since Sun 2019-04-28 14:44:21 PDT; 9min ago Docs: man:systemd-resolved.service(8) https://www.freedesktop.org/wiki/Software/systemd/resolved https://www.freedesktop.org/wiki/Software/systemd/writing-network-configuration-managers https://www.freedesktop.org/wiki/Software/systemd/writing-resolver-clients Main PID: 1010 (systemd-resolve) Status: "Processing requests..." Tasks: 1 (limit: 4915) Memory: 4.3M CGroup: /system.slice/systemd-resolved.service └─1010 /lib/systemd/systemd-resolved Apr 28 14:44:10 Crynfyd systemd[1]: Starting Network Name Resolution... Apr 28 14:44:14 Crynfyd systemd-resolved[1010]: Positive Trust Anchors: Apr 28 14:44:14 Crynfyd systemd-resolved[1010]: . IN DS 19036 8 2 49aac11d7b6f6446702e54a1607371607a1a41855200fd2ce1cdde32f24e8fb5 Apr 28 14:44:14 Crynfyd systemd-resolved[1010]: . IN DS 20326 8 2 e06d44b80b8f1d39a95c0b0d7c65d08458e880409bbc683457104237c7f8ec8d Apr 28 14:44:14 Crynfyd systemd-resolved[1010]: Negative trust anchors: 10.in-addr.arpa 16.172.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 168.192.in-addr.arpa d.f.ip6.arpa corp home internal intranet lan local private test Apr 28 14:44:14 Crynfyd systemd-resolved[1010]: Using system hostname 'Crynfyd'. Apr 28 14:44:21 Crynfyd systemd[1]: Started Network Name Resolution. Apr 28 14:50:13 Crynfyd systemd-resolved[1010]: Using degraded feature set (UDP) for DNS server 192.168.1.1.
Apr 28 14:50:13 Crynfyd systemd-resolved[1010]: Using degraded feature set (UDP) for DNS server 192.168.1.1.
Well this is bizarre. I don't know why it should start working several minutes after bootup.
PS I should mention two things: During the upgrade, somehow most of kde got whacked. I reinstalled kubuntu-desktop, and all SEEMS well, but maybe not. Also, the network problem exists both from the console and from inside kde.
Comment