[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Temporary failure in name resolution



On 3/31/2021 4:21 AM, 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

With a desktop environment (Mate/Gnome...)?

installed according to whereis.

# cat /etc/resolv.conf
domain attlocal.net
search attlocal.net
nameserver 192.168.1.254

If that's not the right nameserver then what is?

IS the DNS serverat 192.168.1.254 working?


$ 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


Are those pings done on the server or on the clients?

# 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?

  - Dan Norton


Did you do a 'systemctl reboot' to restart the server?

--
John Doe


Reply to: