temporary failure in name resolution

nixIT · 2020-12-16 20:25:07

hello all,

hope everyone is staying safe and healthy.

quick question, I have been getting what appears as dropped from the network randomly today. I've rebooted and that didn't help. upon further investigation, when I am not connected I issue the following:

ping google.com

and the following is returned:

temporary failure in name resolution

I immediately try:

ping 8.8.8.8

and the correct results are returned.

I changed nameservers in resolv.con and rebooted but that didn't appear to help.

has anyone else noticed this recently? any ideas what to look for?

--nixIT

seth · 2020-12-16 21:16:44

Do you use systemd-resolved?

ps aux | grep resolved
stat /etc/resolv.conf
cat /etc/resolv.conf
cat /etc/nsswitch.conf

nixIT · 2020-12-17 19:32:56

@seth,

$ ps aux | grep resolved
systemd+   12449  0.0  0.0  23980 11576 ?        Ss   Dec16   0:07 /usr/lib/systemd/systemd-resolved
nixit     120979  0.0  0.0   6384  2332 pts/0    S+   13:01   0:00 grep resolved

$ stat /etc/resolv.conf
  File: /etc/resolv.conf
  Size: 311       	Blocks: 8          IO Block: 4096   regular file
Device: 802h/2050d	Inode: 3407888     Links: 1
Access: (0644/-rw-r--r--)  Uid: (    0/    root)   Gid: (    0/    root)
Access: 2020-12-16 15:35:59.996479355 -0500
Modify: 2020-12-16 15:35:59.946480125 -0500
Change: 2020-12-16 15:35:59.946480125 -0500
 Birth: 2018-06-24 13:08:35.635256157 -0400

$ cat /etc/resolv.conf
# Generated by resolvconf
domain networx.local

# cloudflare
# nameserver 1.1.1.1
# nameserver 1.0.0.1

# opendns
# nameserver 208.67.222.222
# nameserver 208.67.220.220

# quad9
nameserver 9.9.9.9
nameserver 149.112.112.112

# google
# nameserver 8.8.8.8
# nameserver 8.8.4.4

$ cat /etc/nsswitch.conf
# Name Service Switch configuration file.
# See nsswitch.conf(5) for details.

passwd: files systemd
group: files systemd
shadow: files

publickey: files

hosts: files mymachines myhostname resolve [!UNAVAIL=return] dns
networks: files

protocols: files
services: files
ethers: files
rpc: files

netgroup: files

seth · 2020-12-17 20:22:56

Is "networx.local" the mdns domain for the localhost?
Why is that entry there? There's no mdns responder configured in nsswitch, do you configure resolved to act as mdns responder? Can you resolve the domain?
Also why does it use the deprecated "domain" syntax (instead of "search")

Fyi, systemd-resolved isn't good at DNS cascades, https://edgeofsanity.net/rant/2017/12/2 … roken.html but yours looks more like a "try what works" result anyway?
Also ensure to have read and understood https://wiki.archlinux.org/index.php/Sy … solved#DNS (because of "stat /etc/resolv.conf")

nixIT · 2020-12-17 20:45:03

@seth,

thanx for responding quickly and all this info. to be honest, my main rig has been running for years, I think the last install was 4 years ago, and I've just been doing updates since. when I notice something needs to be removed, etc (from arch home page) I will perform those action, otherwise I just let the system run. if some of these things have been deprecated I either missed the notice, or haven't taken a look.

I guess I have some updating system files to do, and quite possibly I might do a fresh install, wanted to get a bigger drive anyway.

yes, networx.local is the name of my local domain, It's been there for years. lol.

thanx again for all your info, off to read up on it.

~nixit

seth · 2020-12-17 20:57:36

yes, networx.local is the name of my local domain, It's been there for years.

Get rid of that - the localhost is searched by default anyway and anything ".local" is prone to conflict w/ mdns resolution.

Arch Linux

#1 2020-12-16 20:25:07

temporary failure in name resolution

#2 2020-12-16 21:16:44

Re: temporary failure in name resolution

#3 2020-12-17 19:32:56

Re: temporary failure in name resolution

#4 2020-12-17 20:22:56

Re: temporary failure in name resolution

#5 2020-12-17 20:45:03

Re: temporary failure in name resolution

#6 2020-12-17 20:57:36

Re: temporary failure in name resolution

Board footer