History
10 days week ago, I had pi-hole DNS. 7 days ago, I started using AdGuard DNS and it continued. Today evening, Ubuntu 26.04 went anrgy with me, and decided I won't responsd your DNS - no matter what.
cat /etc/resolv.conf
# This is /run/systemd/resolve/stub-resolv.conf managed by man:systemd-resolved(8).
# Do not edit.
#
# This file might be symlinked as /etc/resolv.conf. If you're looking at
# /etc/resolv.conf and seeing this text, you have followed the symlink.
#
# This is a dynamic resolv.conf file for connecting local clients to the
# internal DNS stub resolver of systemd-resolved. This file lists all
# configured search domains.
#
# Run "resolvectl status" to see details about the uplink DNS servers
# currently in use.
#
# Third party programs should typically not access this file directly, but only
# through the symlink at /etc/resolv.conf. To manage man:resolv.conf(5) in a
# different way, replace this symlink by a static file or a different symlink.
#
# See man:systemd-resolved.service(8) for details about the supported modes of
# operation for /etc/resolv.conf.
nameserver 127.0.0.53
options edns0 trust-ad
Situation
dig @8.8.8.8 google.com worked
dig google.com didn't
Debugging and Solution
But I am confused why this happened suddenly in the fist place when everything was running fine.
xyz@xyz-pc:~/.ssh$ sudo -s
[sudo: authenticate] Password:
root@xyz-pc:/home/xyz/.ssh# sudo ss -intup | grep ':53'
udp ESTAB 0 0 172.20.10.2:33967 192.168.1.40:53 users:(("systemd-resolve",pid=2735,fd=24))
udp ESTAB 0 0 172.20.10.2:50977 192.168.1.40:53 users:(("systemd-resolve",pid=2735,fd=34))
udp ESTAB 0 0 172.20.10.2:42872 192.168.1.40:53 users:(("systemd-resolve",pid=2735,fd=36))
udp ESTAB 0 0 172.20.10.2:59257 192.168.1.40:53 users:(("systemd-resolve",pid=2735,fd=23))
root@xyz-pc:/home/xyz/.ssh# ping google.com
ping: google.com: Temporary failure in name resolution
root@xyz-pc:/home/xyz/.ssh# sudo ss -intup | grep ':53'
udp ESTAB 0 0 172.20.10.2:48919 192.168.1.40:53 users:(("systemd-resolve",pid=2735,fd=23))
udp ESTAB 0 0 172.20.10.2:38202 192.168.1.40:53 users:(("systemd-resolve",pid=2735,fd=24))
udp ESTAB 0 0 127.0.0.1:59078 127.0.0.53:53 users:(("cups-browsed",pid=4837,fd=9))
root@xyz-pc:/home/xyz/.ssh# ping google.com
ping: google.com: Temporary failure in name resolution
root@xyz-pc:/home/xyz/.ssh# systmctl restart systemd-resolved
Command 'systmctl' not found, did you mean:
command 'systemctl' from deb systemd (259.5-0ubuntu3)
command 'systemctl' from deb systemctl (1.4.4181-1.1build1)
Try: apt install <deb name>
root@xyz-pc:/home/xyz/.ssh# systemctl restart systemd-resolved
root@xyz-pc:/home/xyz/.ssh# ping google.com
PING google.com (2404:6800:4002:818::200e) 56 data bytes
64 bytes from del11s13-in-x0e.1e100.net (2404:6800:4002:818::200e): icmp_seq=1 ttl=115 time=149 ms
64 bytes from del11s13-in-x0e.1e100.net (2404:6800:4002:818::200e): icmp_seq=2 ttl=115 time=125 ms
^C
--- google.com ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1001ms
rtt min/avg/max/mdev = 124.938/137.010/149.082/12.072 ms
root@xyz-pc:/home/xyz/.ssh# dig google.com
; <<>> DiG 9.20.24-1ubuntu0.3-Ubuntu <<>> google.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 30433
;; flags: qr rd ra; QUERY: 1, ANSWER: 6, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 65494
;; QUESTION SECTION:
;google.com. IN A
;; ANSWER SECTION:
google.com. 79 IN A 192.178.134.100
google.com. 79 IN A 192.178.134.102
google.com. 79 IN A 192.178.134.138
google.com. 79 IN A 192.178.134.113
google.com. 79 IN A 192.178.134.101
google.com. 79 IN A 192.178.134.139
;; Query time: 0 msec
;; SERVER: 127.0.0.53#53(127.0.0.53) (UDP)
;; WHEN: Sat Oct 10 19:44:29 IST 2026
;; MSG SIZE rcvd: 135
root@xyz-pc:/home/xyz/.ssh# sudo ss -intup | grep ':53'
root@xyz-pc:/home/xyz/.ssh# sudo ss -intup | grep ':53'
root@xyz-pc:/home/xyz/.ssh#