Name resolution/DNS not working on Pi Zero W after install

[cyberpunkrocker]

A few days ago I bought my first Raspberry Pi, a Zero W. I installed Arch ARM on it, and configured wpa_supplicant during the installation (as per these instructions https://ladvien.com/installing-arch-linux-raspberry-pi-zero-w/). That went quite well, rp0w booted without problems, I could SSH in, I could ping internet by ip addresses, BUT.... I never could get the name resolution working with default settings & programs. To have a working name resolution, I had to 1) stop and disable both systemd-networkd and systemd-resolved, 2) start and enable dhcpcd on wlan0 and 3) edit /etc/resolv.conf by hand. (to stop dhcpcd overwriting it I added 'nohook resolv.conf' to /etc/dhcpcd.conf). I should also mention that none of the other computers in my network has any problems with DNS or routing, including the two other Arch Linux machines (those two are using NetworkManager, though)

Any ideas why systemd-resolved couldn't do its job? According to a quick search through these forums it seems like quite a few new users have the same problem...

[ramsey]

I have a similar problem. sudo systemctl stop systemd-resolved.service works to get networking going. If I disable it, then I have to start and stop systemd-resolved to get a working network connection. In my case, using a chromebook plus.

[ramsey]

I believe I found the cause of my problem here. Checking systemctl status systemd-resolved, I see several messages about DNSSEC validation failed. It seems this change, https://bugs.archlinux.org/task/59391 resulted in DNSSEC being flipped on. So I added to my /etc/systemd/resolved.conf, DNSSEC=no and now my DNS will work after a reboot without stopping systemd-resolved.

[muteki]

I have tried DNSSEC=no and DNS resolution will work for 5 minutes, then I need to restart systemd-resolved to get another 5 minutes of DNS resolution.

Any other clues of where I can look to fix this very annoying issue?

[hmeyer]

that's an old story, have a look here: https://bbs.archlinux.de/viewtopic.php?id=32020

in my case, I put DNSSEC=no in /etc/systemd/resolved.conf
(resolve.conf or resolv.conf don't exit on my raspi 3)

worked for me on raspi 2 (last year) and raspi 3 (some weeks ago)

[muteki]

$this->bbcode_second_pass_quote('hmeyer', 't')hat's an old story, have a look here: https://bbs.archlinux.de/viewtopic.php?id=32020