[Solved] Temporary failure in name resolution(yes it was the resolver)

vert9 · 2023-04-02 13:52:08

After trying out different things and consulting the wiki for hours, I finally think it is best to find help here.

These are the outputs when trying to ping google.com:

$ ping 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: icml_seq=1 ttl=112 time=7.75ms
64 bytes from 8.8.8.8: icml_seq=2 ttl=112 time=7.61ms
64 bytes from 8.8.8.8: icml_seq=3 ttl=112 time=7.74ms
^C
--- 8.8.8.8 ping statistics ---
3 packets transmitted, 3 received, 0% packer loss, time 2004ms

$ ping www.google.com
ping: www.google.com: Temporary failure in name resolution

What I think is that something is wrong with the name resolver. I was able to resolve the www.google.com domain when running the OS on the installation drive, and tried installing Glibc resolver onto the drive. Unfortunately, I still have this same issue. Not sure what is going on, so please help as it is affecting pacman too.

Currently using iwd for wlan connection. Some additional details that might show that my connection is definitely working:

$ ip a
1: lo: <LOOPBACK,UP,LOWERUP> 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
        inet6 ::1/128 scope host
                valid_lft forever preferred_lft forever
...
4: wlan0: <BROADCAST,MULTICAST,UP,LOWERUP> mtu 1500 qdisc noqueue state UP group default qlen 1000
        link/ether 84:7b:57:2c:9d:27 brd ff:ff:ff:ff:ff:ff
        inet 192.168.1.123/24 scope global dynamic noprefixroute wlan0
                valid_lft 13821sec preferred_lft 13821sec
        inet6 fe80::867b:57ff:fe2c:9d27/64 scope link
                valid_lft forever preferred_lft forever

$ ip route
default via 192.168.1.254 dev wlan0 proto dhcp src 192.168.1.123 metric 304
192.168.1.0/24 dev wlan0 proto dhcp scope link metric 304

$ ip -6 route
::1 dev lo proto kernel metric 256 pref medium
fe:80::/64 dev wlan0 proto kernel metric 256 pref medium

Last edited by vert9 (2023-04-02 16:07:57)

seth · 2023-04-02 14:10:47

Please post the output of

find /etc/systemd -type l -exec test -f {} \; -print | awk -F'/' '{ printf ("%-40s | %s\n", $(NF-0), $(NF-1)) }' | sort -f

Please also edit your post and wrap the command IO in "code" tags, https://bbs.archlinux.org/help.php#bbcode

vert9 · 2023-04-02 14:31:35

Hi, yes my apologies. Will edit the first post

$ find /etc/systemd -type l -exec test -f {} \; -print | awk -F'/' '{ printf ("%-40s | %s\n", $(NF-0), $(NF-1)) }' | sort -f
display-manager.service          |system
getty@ttyl.service              |getty.target.wants
pll-kit-server.socket           |sockets.target.wants
remote-fs.target                |multi-user.target.wants

seth · 2023-04-02 14:34:52

How do you configure the network to begin with?
There's no network configuring daemon.

Edit

Currently using iwd for wlan connection.

Incl. https://wiki.archlinux.org/title/Iwd#En … figuration ?

Last edited by seth (2023-04-02 14:35:55)

vert9 · 2023-04-02 14:53:58

This is my config file (/etc/iwd/main.conf):

[General]
EnableNetworkConfiguration=true

[Network]
RoutePriorityOffset=300
EnableIPv6=true
NameResolvingService=resolveconf

For NameResolvingService, I also tried 'systemd'.

seth · 2023-04-02 15:00:07

Don't run services concurrently.

What's the output of

dig google.com # dig is part of the bind package
dig @8.8.8.8 google.com
cat /etc/resolv.conf

vert9 · 2023-04-02 16:04:46

Hi, thanks for probing me to think along the lines of services and configuration files... I managed to solve this and can go to bed now yay!

I realised that the resolvconf service did not exist, but systemd-resolved did (and strangely enough it was disabled and dead).

So I restarted and enabled the 'systemd-resolved' service, modified the iwd configuration file (/etc/iwd/main.conf)

[Network]
NameResolvingService=systemd

and finally restarted the iwd service, which fixed the whole problem. Thanks and sorry for the trouble! :')

Arch Linux

#1 2023-04-02 13:52:08

[Solved] Temporary failure in name resolution(yes it was the resolver)

#2 2023-04-02 14:10:47

Re: [Solved] Temporary failure in name resolution(yes it was the resolver)

#3 2023-04-02 14:31:35

Re: [Solved] Temporary failure in name resolution(yes it was the resolver)

#4 2023-04-02 14:34:52

Re: [Solved] Temporary failure in name resolution(yes it was the resolver)

#5 2023-04-02 14:53:58

Re: [Solved] Temporary failure in name resolution(yes it was the resolver)

#6 2023-04-02 15:00:07

Re: [Solved] Temporary failure in name resolution(yes it was the resolver)

#7 2023-04-02 16:04:46

Re: [Solved] Temporary failure in name resolution(yes it was the resolver)

Board footer