Re: Temporary failure in name resolution
On 3/30/21 7:21 PM, Dan Norton wrote:
After the 10.9 upgrade, name resolution is not working for me. Does anyone else see this?
My desktop is a wifi server for laptop access using windows. That works OK but the server, attached by ethernet to the DSL modem does not get names resolved since the upgrade. The resolvconf program is not installed according to whereis.
# cat /etc/resolv.conf
domain attlocal.net
search attlocal.net
nameserver 192.168.1.254
Have you done a cold reboot since upgrading Debian?
Do the following commands indicate everything is up to date?
# apt-get update
# apt-get upgrade
Have you changed any of the gateway settings recently?
Please verify that the DNS proxy server on the gateway is working by
testing name resolution with another computer.
I have a ~2007 Dell Inspiron E1505 laptop with Debian 10:
2021-03-30 22:29:53 dpchrist@dipsy ~
$ cat /etc/debian_version ; uname -a
10.9
Linux dipsy 4.19.0-16-amd64 #1 SMP Debian 4.19.181-1 (2021-03-19) x86_64
GNU/Linux
I have AT&T U-verse residential VDSL service. When I connect the E1505
to the gateway via Ethernet and DHCP:
2021-03-30 22:47:40 root@dipsy ~
# ifconfig eth0
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.1.149 netmask 255.255.255.0 broadcast 192.168.1.255
inet6 ****::****:****:****:**** prefixlen 64 scopeid 0x20<link>
inet6 2600:170*:****:****:****:****:****:**** prefixlen 64
scopeid 0x0<global>
ether **:**:**:**:**:** txqueuelen 1000 (Ethernet)
RX packets 11184 bytes 935656 (913.7 KiB)
RX errors 0 dropped 41 overruns 0 frame 0
TX packets 1911 bytes 255554 (249.5 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device interrupt 17
2021-03-30 22:48:19 root@dipsy ~
# cat /etc/resolv.conf
# Generated by NetworkManager
search attlocal.net
nameserver 192.168.1.254
nameserver 2600:170*:****:****::1
Both IPv4 and IPv6 "nameserver" addresses correspond to the LAN side of
the gateway. ('*' is for redacted characters.)
If that's not the right nameserver then what is?
$ ping google.com
ping: google.com: Temporary failure in name resolution
$ ping -c2 8.8.8.8
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
64 bytes from 8.8.8.8: icmp_seq=1 ttl=117 time=21.1 ms
64 bytes from 8.8.8.8: icmp_seq=2 ttl=117 time=21.2 ms
--- 8.8.8.8 ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 2ms
rtt min/avg/max/mdev = 21.148/21.188/21.229/0.151 ms
# systemctl status systemd-resolved
shows it being active and "Processing requests...".
Nothing in history.log and term.log is obviously wrong to me FWIW.
# journalctl -b0
gives no clue to me.
No doubt it is something simple(tm). Where should I look or what should I re-read?
Please run the following commands. Use Ctrl+C to interrupt any commands
that hang. Reply with your complete console session -- prompts,
keystrokes entered, and output displayed. Redact as desired:
$ cat /etc/debian_version ; uname -a
$ ping -c 3 192.168.1.254
$ nmcli g status
$ nmcli c show
$ nmcli d show
$ host -v -t A www.debian.org 8.8.8.8
$ host -v -t A www.debian.org
David
Reply to: