Besides the connection test the Ret seems to be working
No. Yesterday when I installed MATE GUI and login to desktop. Firefox was not able to reach any sites.
and now I try to install MATE again and got this, same as all past errors.
│ Checking DNS resolver │
│ - Command: ping -c 1 -W 10 dns9.quad9.net │
│ - Exit code: 2 │
│ - DietPi version: v7.0.2 (MichaIng/master) | HW_MODEL: 20 | HW_ARCH: 10 | DISTRO: 5 │
│ - Image creator: DietPi Core Team │
│ - Pre-image: Debian mini.iso │
│ - Error log: │
│ ping: dns9.quad9.net: Temporary failure in name resolution │
│ │
│ 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 │
│ │
│ │
│ <Ok> <Exit> │
│ │
└──────────────────────────────────────────────────────────────────────────────────────────────────┘
But the same ping test to Quad9 was working well before
ping -c 1 -W 10 dns9.quad9.net
Seems something with your VM or did you changed anything in between?
But the same ping test to Quad9 was working well before
Yep.
Seems something with your VM or did you changed anything in between?
No.
===
Tried to send bug report, don’t know if it succeeded.
| IP: 192.168.0.5 | Use up/down buttons to scroll text────────────────────┐
│ Sending bug report
│ - Command: curl --connect-timeout 8 --retry 1 --retry-delay 4 -sSvT
│ ec452965-67f0-4d82-b444-11a546566d54.7z
│ sftp://dietpi-survey:upload2dietpi@ssh.dietpi.com:22/bugreport/
│ - Exit code: 28
│ - DietPi version: v7.0.2 (MichaIng/master) | HW_MODEL: 20 | HW_ARCH: 10 | DISTRO: 5
│ - Image creator: DietPi Core Team
│ - Pre-image: Debian mini.iso
│ - Error log:
│ * Expire in 0 ms for 6 (transfer 0x560af633ffb0)
│ * Expire in 8000 ms for 2 (transfer 0x560af633ffb0)
│ * Expire in 1 ms for 1 (transfer 0x560af633ffb0)
│ * Expire in 0 ms for 1 (transfer 0x560af633ffb0)
│ * Expire in 1 ms for 1 (transfer 0x560af633ffb0)
│ * Expire in 0 ms for 1 (transfer 0x560af633ffb0)
│ * Expire in 0 ms for 1 (transfer 0x560af633ffb0)
│ * Expire in 1 ms for 1 (transfer 0x560af633ffb0)
│ * Expire in 0 ms for 1 (transfer 0x560af633ffb0)
│ * Expire in 0 ms for 1 (transfer 0x560af633ffb0)
│ * Expire in 1 ms for 1 (transfer 0x560af633ffb0)
│ * Expire in 0 ms for 1 (transfer 0x560af633ffb0)
│ * Expire in 0 ms for 1 (transfer 0x560af633ffb0)
│
│ Retry : Re-run the last command that failed ↑
│ DietPi-Config : Edit network, APT/NT
This did not worked. Can you run again
ping -c 1 -W 10 dns9.quad9.net
root@DietPi:~# ping -c 1 -W 10 dns9.quad9.net
ping: dns9.quad9.net: Temporary failure in name resolution
==
from Windows
C:\Windows\system32>ping dns9.quad9.net
Pinging dns9.quad9.net [149.112.112.9] with 32 bytes of data:
Reply from 149.112.112.9: bytes=32 time=84ms TTL=56
Reply from 149.112.112.9: bytes=32 time=79ms TTL=56
Reply from 149.112.112.9: bytes=32 time=40ms TTL=56
Reply from 149.112.112.9: bytes=32 time=43ms TTL=56
Ping statistics for 149.112.112.9:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 40ms, Maximum = 84ms, Average = 61ms
Are you using same DNS server on windows as well as on the VM?
But as said, this was working fine before on another test you did
DNS is 1.1.1.1 and 8.8.8.8 on the router.
and the behavior now is the same behavior as past, always.
DHCP was fine, once switched to static, it stopped working immediately.
Could you test yourself using the VM image on the site?
Can you change DNS to 8.8.8.8 on the VM as well
tested. same result. [Failure]|Offline
OK. found that in Dietpi-Config Quad9 DNS entries are 9.9.9.9 and 149.112.112.112
But on Windows using ping
ping dns9.quad9.net got
Pinging dns9.quad9.net [149.112.112.9] with 32 bytes of data:
Reply from 149.112.112.9: bytes=32 time=84ms TTL=56
Reply from 149.112.112.9: bytes=32 time=79ms TTL=56
Reply from 149.112.112.9: bytes=32 time=40ms TTL=56
Reply from 149.112.112.9: bytes=32 time=43ms TTL=56
does it make a difference?
112 at the end is correct as you can see on this overview. https://en.m.wikipedia.org/wiki/Public_recursive_name_server
pinging ip address is OK in DietPi, but ping a name got Temporary failure in name resolution error.
What’s the command to find out what DNS server I’m using on Linux?
And what’s the equivalent of Windows NSLookup?
cat /etc/resolv.conf
Should be configured in this file
8.8.8.8
Answering my own question: need to execute the following command to install
apt install dnsutils
==
I switched back to DHCP and ping www.firefox.com and it immediately worked.
ping www.firefox.com
PING dzlgdtxcws9pb.cloudfront.net (13.33.185.129) 56(84) bytes of data.
64 bytes from server-13-33-185-129.sea19.r.cloudfront.net (13.33.185.129): icmp_seq=1 ttl=242 time=153 ms
If static IP then will get Temporary failure in name resolution error.
root@DietPi:~# ping www.firefox.com
ping: www.firefox.com: Temporary failure in name resolution
So the verdict is:
Whenever dietpi-software launches, it will run
ping -c 1 -W 10 dns9.quad9.net
no matter what DNS entries I set at ethernet network configuration
It always fails if I set static IP for the VM, and
it always succeeds if I use DHCP for the VM.
And dietpi-software is not able to continue further if the command
ping -c 1 -W 10 dns9.quad9.net fails.
well, actually every ping command that pings a full qualified domain name fails once static IP is set.
I downloaded and installed the Native PC for BIOS/CSM image on a physical machine, exactly the same issue.
Once set a static IP, DNS resolver doesn’t work and Dietpi-Software refuses to proceed.
Sounds like a port security issue.
Have you tried to change to static IP other devices in the network or only this PC?
Can you tell us more about the topology that you have?
Very simple topology.
Only 2 PCs and Android smartphones devices behind DSL modem + router in 192.168.0.x range. Main PC running VMWare pro 16. x86 VM using bridged network card that ether bridged to main PC’s Intel gigabit network card with IPv4/IPv6/etc protocols that Windows 10 installed or to a Realtek Gigabit USB 3.0 adapter which removed all protocols except VMware Bridged Protocol, same result.
Also the same result for the other physical PC.
Therefore it has something to do with the modem/router, not dietpi.