Expected Behaviour:
Able to access amazon.com, .co.uk and .com.au
-operating system
Linux PiHole 5.10.103-v7+ #1529 SMP Tue Mar 8 12:21:37 GMT 2022 armv7l
Actual Behaviour:
xxx@xxx:~ $ ping amazon.com
ping: amazon.com: Temporary failure in name resolution
xxx@xxx:~ $ ping amazon.co.uk
ping: amazon.co.uk: Temporary failure in name resolution
xxx@xxx:~ $ ping amazon.com.au
PING amazon.com.au (52.119.174.16) 56(84) bytes of data.
64 bytes from 52.119.174.16 (52.119.174.16): icmp_seq=1 ttl=238 time=220 ms
Debug Token:
https://tricorder.pi-hole.net/Yb3kDi4K/
Your output suggests that amazon.com.au
is resolving correctly, contradicting your title?
Anway, note that ping
is not adequate to analyse DNS issues, as it uses additional means of resolving hostnames, not just plain DNS.
What's the output of:
nslookup amazon.com
nslookup amazon.com.au
Likely unrelated to your issue, but your debug log shows you run a rather old version of Pi-hole (v4.3 from 2019).
system
Closed
5
This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.