Arch Linux

fish_monster

Member

Registered: 2022-02-21

Posts: 15

Temporary Failure in Name Resolution

I have the following issue:

[****@****]$ ping google.com
ping: google.com: Temporary failure in name resolution

(and I cannot load a website in the browser).

But I can successfully ping 8.8.8.8.

Here is the output of "ip a"

[****@**** ~]$ ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
2: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group 57841 qlen 1000
    link/ether 28:7f:cf:08:bf:c9 brd ff:ff:ff:ff:ff:ff
    inet 192.168.12.233/24 brd 192.168.12.255 scope global dynamic noprefixroute wlan0
       valid_lft 591653sec preferred_lft 591653sec
    inet 192.168.12.234/24 brd 192.168.12.255 scope global secondary dynamic noprefixroute wlan0
       valid_lft 604050sec preferred_lft 528450sec
4: nordtun: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UNKNOWN group default qlen 500
    link/none 
    inet 10.100.0.2/21 scope global nordtun
       valid_lft forever preferred_lft forever

And of "ip r":

[****@**** ~]$ ip r
default via 192.168.12.1 dev wlan0 proto dhcp src 192.168.12.234 metric 3002 
default via 192.168.12.1 dev wlan0 proto dhcp src 192.168.12.233 metric 20600 
192.168.12.0/24 dev wlan0 proto kernel scope link src 192.168.12.233 metric 600 
192.168.12.0/24 dev wlan0 proto dhcp scope link src 192.168.12.234 metric 3002 

And of possible interest:

[****@**** ~]$ find /etc/systemd -type l -exec test -f {} \; -print | awk -F'/' '{ printf ("%-40s | %s\n", $(NF-0), $(NF-1)) }' | sort -f
atd.service                              | multi-user.target.wants
avahi-daemon.service                     | multi-user.target.wants
avahi-daemon.socket                      | sockets.target.wants
bluetooth.service                        | bluetooth.target.wants
cups.path                                | multi-user.target.wants
cups.service                             | multi-user.target.wants
cups.service                             | printer.target.wants
cups.socket                              | sockets.target.wants
dbus-org.bluez.service                   | system
dbus-org.freedesktop.Avahi.service       | system
dbus-org.freedesktop.nm-dispatcher.service | system
dbus-org.freedesktop.resolve1.service    | system
dbus-org.freedesktop.timesync1.service   | system
dhcpcd.service                           | multi-user.target.wants
display-manager.service                  | system
gcr-ssh-agent.socket                     | sockets.target.wants
getty@tty1.service                       | getty.target.wants
gnome-keyring-daemon.socket              | sockets.target.wants
NetworkManager.service                   | multi-user.target.wants
NetworkManager-wait-online.service       | network-online.target.wants
nordvpnd.service                         | default.target.wants
ntpd.service                             | multi-user.target.wants
p11-kit-server.socket                    | sockets.target.wants
pipewire.socket                          | sockets.target.wants
postgresql.service                       | multi-user.target.wants
pulseaudio.socket                        | sockets.target.wants
remote-fs.target                         | multi-user.target.wants
systemd-resolved.service                 | sysinit.target.wants
systemd-timesyncd.service                | sysinit.target.wants
vpnagentd.service                        | multi-user.target.wants

Last edited by fish_monster (2025-02-03 19:55:45)

Head_on_a_Stick

Member

From: The Wirral

Registered: 2014-02-20

Posts: 8,824

Website

Re: Temporary Failure in Name Resolution

What is the status of /etc/resolv.conf?

I think NetworkManager is supposed to populate it, and it leaves a message to the effect in a comment at the top.

More details here: https://wiki.archlinux.org/title/Networ … management

The VPN may be a factor here. I know _nothing_ about VPNs (sorry).

---

Jin, Jîyan, Azadî

V1del

Forum Moderator

Registered: 2012-10-16

Posts: 24,118

Re: Temporary Failure in Name Resolution

disable dhcpcd service. unless you specifically reconfigured NM to use it you don't want it active. That said also agree, the active nordvpn might be a big cause here, iirc their tooling includes a killswitch that you'd want to disable.