DNS resolver fails every time on IPV6 only connection

I’m on starlink, which is behind a CGNAT but does offer ipv6 if you know how to force the solicitations and run native ipv6 (so i can access my home server remotely). So ultimately, I have an ipv6 only connection.

The only downside of this has been that dietpi fails every single time when it attempts to verify network connectivity (such as when I update or download new software).

Thankfully, I can just edit the command and change “one.one.one.one” to “localhost” and it, of course, resolves. It functions normally after that. Its been this way for many months. I strongly suspect its due to my ipv6 only connection, but its been more of a nuisance than a problem… so I’m only now mentioning it.

 Step: Checking for prerequisite software

[  OK  ] DietPi-Software | Checking network connectivity
[FAILED] DietPi-Software | Checking DNS resolver
 - Command: ping -nc 1 -W 10 one.one.one.one
[ INFO ] DietPi-Software | Executing alternative command: ping -nc 1 -W 10 localhost
PING localhost(::1) 56 data bytes
64 bytes from ::1: icmp_seq=1 ttl=64 time=0.023 ms

--- localhost ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 0.023/0.023/0.023/0.000 ms
[  OK  ] Alternative command execution | Completed
[  OK  ] Network time sync | Completed
[ SUB1 ] DietPi-Services > unmask

What does ping is returning

ping -nc 1 -W 10 one.one.one.one
ping -nc 1 -W 10
ping -nc 1 -W 10 google.com

Could you also post the following?

ip addr; cat /etc/resolv.conf; cat /etc/network/interfaces

You can alter the sensitive part of a public IPv6, but keep it consistent.

I ran the commands and shortly thereafter realized an issue with my ipv6 solicitation script was to blame. It’s completely external to dietpi. It’s working properly now. This thread can be deleted.