Comment 37 for bug 1934221

Revision history for this message
Denys Fedoryshchenko (nuclearcat) wrote :

My system is focal. Can't try Hirsute yet, dont have any systems with such error appearing.

It doesnt work at all for me, fail to resolve anything

Link 2 (enp3s0)
      Current Scopes: DNS
DefaultRoute setting: yes
       LLMNR setting: yes
MulticastDNS setting: no
  DNSOverTLS setting: no
      DNSSEC setting: no
    DNSSEC supported: no
  Current DNS Server: 2a0d:e40:0:4000::1
         DNS Servers: 2a0d:e40:0:4000::1
                      fd2c:bf12:1194::1
                      10.255.255.1
                      8.8.8.8
          DNS Domain: ~.
                      spinesystems.solutions

udp 0 0 127.0.0.53:53 0.0.0.0:* 4106635/systemd-res
resolv.conf nameserver: nameserver 127.0.0.53

dig @127.0.0.53

; <<>> DiG 9.16.1-Ubuntu <<>> @127.0.0.53
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 4404
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 65494
;; QUESTION SECTION:
;. IN NS

;; Query time: 0 msec
;; SERVER: 127.0.0.53#53(127.0.0.53)
;; WHEN: Mon Oct 04 12:34:50 EEST 2021
;; MSG SIZE rcvd: 28

dig +short @2a0d:e40:0:4000::1 www.google.com
142.250.200.196

# systemd-resolve -4 www.google.com
www.google.com: resolve call failed: No appropriate name servers or networks for name found

But didnt rebooted yet after fetching new systemd.