depends, you would need to check the exact error message while running the command
ping -c 1 dns9.quad.net
ping -c 1 9.9.9.9
usually both should return same result
I am having the exact same issue, the only difference is that I dont use IPV6 as far as I know. Is my first time trying dietpi and I downloaded the image that is available today Jan 26, 2022 and after put it in the PI and boot I get the exact same thing. I can ping from the device google, yahoo, 8.8.8.8, etc but there is not way to ping dns9.quad9.net. I even changed the dns on my network from pihole straight to 8.8.8.8 and rebooted the PI, same issue, I disabled ipv6 in the PI and same thing. But I can ping it from my PC, Is like something in the pre-installation of the dietpi dont allow to ping that. I see IPV6 turned off on my Unifi UDM Pro so I assume I am not running ipv6.
I just noticed that I can ping 9.9.9.9 without issues, but absolutely not the dns address, I get back: ping: dns9.quad9.net: Name or service not known
Can you do some testing. Pls share the results
Following to test Quad9
ping -4 -c 1 dns9.quad9.net
ping -4 -c 1 9.9.9.9
ping -c 1 dns9.quad9.net
ping -c 1 9.9.9.9
Same for Cloudflare
ping -4 -c 1 one.one.one.one
ping -4 -c 1 1.1.1.1
ping -c 1 one.one.one.one
ping -c 1 1.1.1.1
What is the output of
nslookup dietpi.com; host dietpi.com; ls -l /etc/resolv.* /tmp/resolv.*; head -n -0 /etc/resolv/* /tmp/resolv.*
From the PI using the shell:
1- ping -4 -c 1 dns9.quad9.net
ping: dns9.quad9.net: Name or service not known
2- ping -4 -c 1 1.1.1.1
PING 1.1.1.1 (1.1.1.1) 56(84) bytes of data.
64 bytes from 1.1.1.1: icmp_seq=1 ttl=56 time=13.8 ms
— 1.1.1.1 ping statistics —
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 13.802/13.802/13.802/0.000 ms
3- ping -c 1 dns9.quad9.net
ping: dns9.quad9.net: Name or service not known
4- ping -c 1 one.one.one.one
PING one.one.one.one (1.1.1.1) 56(84) bytes of data.
64 bytes from one.one.one.one (1.1.1.1): icmp_seq=1 ttl=56 time=12.2 ms
— one.one.one.one ping statistics —
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 12.178/12.178/12.178/0.000 ms
5- ping -c 1 1.1.1.1
PING 1.1.1.1 (1.1.1.1) 56(84) bytes of data.
64 bytes from 1.1.1.1: icmp_seq=1 ttl=56 time=17.4 ms
— 1.1.1.1 ping statistics —
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 17.388/17.388/17.388/0.000 ms
ok Cloudflare seems to be working, but due to whatever reason Quad9 not. You can adjuste as follow
Do nano /boot/dietpi.txt and search for the following 2 lines:
# General connection and DNS testing
# - IP to ping when checking network connectivity. Default: 1.1.1.1 (Cloudflare DNS, should be very fast world-wide)
CONFIG_CHECK_CONNECTION_IP=1.1.1.1
# - Domain to ping when checking DNS resolver. Default: one.one.one.one (Cloudflare DNS domain, see above)
CONFIG_CHECK_DNS_DOMAIN=one.one.one.one
You simply can switch to one.one.one.one / 1.1.1.1 and retry.
where I am supposed to edit that? directly in the memory card of the PI? because I dont have any /DietPi directory in root.
ahh my fault. Copied an old post. It is located in /boot now.
well, still not working,
Ive found the dietpi.txt inside /boot, when found the text it was like this (notice 9.9.9.9 instead of 1.1.1.1 as you said)
# General connection and DNS testing
# - IP to ping when checking network connectivity. Default: 9.9.9.9 (Quad9 DNS >
CONFIG_CHECK_CONNECTION_IP=9.9.9.9
So I change it to 1.1.1.1, reboot the PI and this is what I get:
[FAILED] Unknown install state/First run setup failed │
│ │
│ An error has occured either during first run update or installs. │
│ │
│ First run setup will now attempt to re-apply the last step, forced as │
│ interactive run. │
│ If this repeatedly fails, please collect all terminal output and the content │
│ of /var/tmp/dietpi/logs/dietpi-firstrun-setup.log if available and report │
│ this issue to: https://github.com/MichaIng/DietPi/issues │
│ │
│ Would you like to restart the first run setup and installation?
I hit ok and the same thing:
Checking DNS resolver │
│ - Command: ping -nc 1 -W 10 dns9.quad9.net │
│ - Exit code: 2 │
│ - DietPi version: v7.9.3 (MichaIng/master) | HW_MODEL: 4 | HW_ARCH: 3 | │
│ DISTRO: 6 │
│ - Image creator: DietPi Core Team │
│ - Pre-image: from scratch │
│ - Error log: │
│ ping: dns9.quad9.net: Name or service not known │
│ │
│ Retry : Re-run the last command that failed │
│ DietPi-Config : Edit network, APT/NTP mirror settings etc │
│ Open subshell : Open a subshell to investigate or solve the issue │
│ Send report : Uploads bugreport containing system info to DietPi │
│ ●─ Devs only ──────────────────────────────────────● │
│ Change command : Adjust and rerun the command
There are 2 values in that configuration section and exactly the important one you missed to change. You need to adjust CONFIG_CHECK_DNS_DOMAIN as well because you are failing on the DNS resolution for Quad9 and not the IP ping
CONFIG_CHECK_CONNECTION_IP=1.1.1.1
CONFIG_CHECK_DNS_DOMAIN=one.one.one.one
Btw, in my example I already changed the values as they should fit best in your case. There was just a need to simply copy it.
opps, sorry I missunderstood…
well, noooooow worked, continuing the installation.
thank you very much for your quick help!!!
Thank you!
Disabling ipv6 solved the same problem here.
1 Like
Hello dear Diet-Pi community,
I am new here and my name is Stefan.
Unfortunately I also have a problem with the installation and the DNS resolver error.
I have switched off ipv6
Dietpi is accessible from the Internet according to the Fritzbox.
I have carried out the ping. However, that doesn’t tell me much. I am new to this area.
DietPi v9.8.0 : 08:55 - Tue 11/19/24
─────────────────────────────────────────────────────
- LAN IP : 192.168.178.111 (eth0)
DietPi-Update
─────────────────────────────────────────────────────
Phase: Checking for available DietPi update
[ OK ] DietPi-Update | Checking IPv4 network connectivity
[FAILED] DietPi-Update | Checking DNS resolver
- Command: getent hosts dns9.quad9.net
[ INFO ] DietPi-Update | Executing alternative command: getent hosts dns9.quad9.net
[FAILED] Alternative command execution | Exited with error
Press any key to return to error handler menu...
[FAILED] DietPi-Update | Unable to continue, DietPi-Update will now terminate.
ping: dns9.quad9.(net): Temporary failure in name resolution
PING 9.9.9.9 (9.9.9.9) 56(84) bytes of data.
64 bytes from 9.9.9.9: icmp_seq=1 ttl=59 time=12.3 ms
--- 9.9.9.9 ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 12.332/12.332/12.332/0.000 ms
ping: dns9.quad9.(net): Temporary failure in name resolution
PING 9.9.9.9 (9.9.9.9) 56(84) bytes of data.
64 bytes from 9.9.9.9: icmp_seq=1 ttl=59 time=12.2 ms
--- 9.9.9.9 ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 12.155/12.155/12.155/0.000 ms
ping: one.one.one.one: Temporary failure in name resolution
PING 1.1.1.1 (1.1.1.1) 56(84) bytes of data.
64 bytes from 1.1.1.1: icmp_seq=1 ttl=52 time=12.5 ms
--- 1.1.1.1 ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 12.478/12.478/12.478/0.000 ms
ping: one.one.one.one: Temporary failure in name resolution
PING 1.1.1.1 (1.1.1.1) 56(84) bytes of data.
64 bytes from 1.1.1.1: icmp_seq=1 ttl=52 time=12.2 ms
--- 1.1.1.1 ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 12.177/12.177/12.177/0.000 ms
What can I do?
Many thanks in advance
Stefan
I had to put .net in parentheses, otherwise I wouldn’t have been able to post it
Please try to use English as we are an international community. For now, I translate your post using DeepL.
Back to your topics, do you use a local DNS server like PiHole? or AGH? Can you check
cat /etc/resolv.conf
Hi Joulinar,
i try to write in english.
I had Dietpi with PiHole on my Pine64. It works fine, but for a few weeks i can´t update and i decided to install all new. Without success
Here ist the answer from putty
domain fritz.box
search fritz.box
nameserver 192.168.178.111
The DNS server was …83 and i hoped, when i change the IP-Adress to the new IP, it will works.
this is currently the DNS server configured. Is this your FritzBox? Which upstream DNS has been set within your router? Should be provider or a global public.
feel free to use tools like deepl.com
Hello,
my first Fritzbox is…1. A 2 Fritzbox is connected to this…45. This is where the Pine64 is connected to the .111
The local DNS server .111 is set up on the first Fritzbox. I’ve now set this back to .1 because I thought it might help.
I don’t know what you mean by upstream DNS?
FritzBox: Use ISP-assigned DNSv4 servers (recommended)