Raspberry Pi 4 DNS Issues

[keflein]

Hello.

I recently purchased a Raspberry Pi 4 and have installed the ARM version of Arch Linux on it. I think I may be having issues with my DNS. I am using netctl to connect to my home router. My netctl profile was generated from wifi-menu. I can connect and I am assigned an IPv4 address, however, I can't ping Google nor can I ping any other machine outside my network. I basically do not have Internet access. I have already tried searching for others who had this issues, and it seems like everyone has different experiences.

I have tried adding the 8.8.8.8 to my resolv.conf, but that will only give me access to some websites.

My output of my netctl config
$this->bbcode_second_pass_code('', '
Description='Automatically generated profile by wifi-menu'
Interface=wlan0
Connection=wireless
Security=wpa
ESSID=home
IP=dhcp
Key=password
')
Output of /etc/resolvconf.conf
$this->bbcode_second_pass_code('', '
# Configuration for resolvconf(8)
# See resolvconf.conf(5) for details

resolv_conf=/etc/resolv.conf
# If you run a local name server, you should uncomment the below line and
# configure your subscribers configuration files below.
#name_servers=127.0.0.1
')
Output of /etc/resolv.conf
$this->bbcode_second_pass_code('', '
# Generated by resolvconf
nameserver 192.168.0.1
')
only managed to setup my desktop environment on my Raspberry Pi 4 because I used an Ethernet cable. In my experiences with setting up KrogerFeedback previous Arch Linux's, you still had to manually specify that you were going to use an Ethernet cable by running dhcpcd. Not so much with the RPI4 because I didn't have to run that command at all. I assume there an enabled service that is possibly interfering with my DNS.

I am very noob when it comes to configuring networks on Arch Linux, so please tell me which commands to run if more information is needed. TYVM.

[summers]

This is another thread on exactly this subject: https://archlinuxarm.org/forum/viewtopic.php?f=9&t=14044.

Really what its about is how to get DNS working in arch, this is documented on the main arch site.

Anyway the short message is "netctl" is the old way of doing network configuration in arch, for some time now the default has been the systemd units systemd-networkd and systemd-resolved. If you are looking for the easy simple way of setting things up, systemd is usually best. So to switch to systemd:

Remove netctl: $this->bbcode_second_pass_code('', 'pacman -R netctl')

Enable and start systemd-network: $this->bbcode_second_pass_code('', 'systemctl enable systemd-networkd.service
systemctl start systemd-networkd.service')

Enable and start systemd-resolved: $this->bbcode_second_pass_code('', 'systemctl enable systemd-resolved.service
systemctl start systemd-resolved.service')

And usually in 90% of cases that will start it working.

To check its working: $this->bbcode_second_pass_code('', 'networkctl status')

Anyway greater picture, is your /etc/resolv.conf is pointing to 192.168.0.1 now that is usually the IP address or your router. Does your router correctly work as a DNS server? Most routers, when connecting to the internet, will mirror the DNS server they are given when negotiating to the internet; and then give out their own IP to any machining connecting to the router. So if your set up isn't working, it may be worth checking your router is working as it should be ...

[lvml]

My personal experience is quite the opposite of that posted by "summers": Only after deactivating "systemd-resolved" I got to a reliable network and especially DNS configuration. "netctl" works fine for me, and unlike "systemd" it makes no weird false assumptions about network being available all the time, stalling boots when that is not the case.

[summers]

From the other thread you posted on, did you establish if its DNSSEC related? This seems to be what has been part of many of the problems seen recently, so the first thing you have to address is can you track the problem back to DNSSEC, or can you rule that out. Only when this is answered can other options be looked into, so just asking the same question again on another thread doesn't help.