Arch Linux

QueenVakarian

Member

Registered: 2019-09-18

Posts: 19

NetworkManager having consistent fails in name resolution

Hello. Recently I've been having issues with NetworkManager losing connection. When this happens I get the error message

Temporary failure in name resolution

when I try and ping out. This is on an ethernet connection. Important note: The router is locked down by the provider, so I'm unable to do any troubleshooting beyond just powering it on and off - which does not seem to help.

Things I've verified when this failure happens:
- systemd-resolve.service is disabled
- dnsmasq does not exist as a service
- dhcpcd does not exist as a service
- ip addr gives me an address
- I can ping 8.8.8.8
- I cannot ping my router - no error message is given it just hangs until I CTRL+C which shows 100% packet loss. (I can ping the router when the connection comes back)
- It happens only to my pc and not my other (which runs Windows)
- The only nameserver listed in my /etc/resolv.conf is my router

At this point I'm at a loss as to where the issue is since nothing has changed about my network configuration since switching providers, as far as I'm aware. I have had multiple issues with the provider's connection since switching, however. Is there something wrong with my configuration where I need to reinstall NetworkManager fresh or is this an issue with the ISPs end?

Last edited by QueenVakarian (2022-10-26 02:52:32)

seth

Member

Registered: 2012-09-03

Posts: 60,805

Re: NetworkManager having consistent fails in name resolution

- I can ping 8.8.8.8
- I cannot ping my router - no error message is given it just hangs until I CTRL+C which shows 100% packet loss. (I can ping the router when the connection comes back)
- The only nameserver listed in my /etc/resolv.conf is my router

So the router provides a DNS server (likely dnsmasq to your ISPs shitty DNS, they're all underdimensioned) but doesn't respond to ICMP requests while apparently still routing (so you can ping googles DNS)
=> Your ISP issued anger temptation device partly breaks service, you don't want to rely on its DNS
==> https://wiki.archlinux.org/title/Networ … NS_servers (1.1.1.1, 8.8.8.8, 9.9.9.9 and there're multiple other open DNS servers)
==> https://wiki.archlinux.org/title/Networ … forwarding is maybe also a good idea since you don't have a (reliable) local DNS but even for the stub resolvers, you don't want your router's IP in there.

Edit: w/ mutliple systems in the LAN and in case your ISP shitbox allows that, I'd degrade it to a pure modem and hook a reasonable router (eg. supported by dd-/openWRT) behind and male that the router, local DNS cache and whatnot.

Last edited by seth (2022-10-26 06:59:35)

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc