20-03-2023 15:25 - edited 20-03-2023 16:20
I’m having issues obtaining a DNS response from four AWS R53 resolvers.
I receive timeouts when querying over UDP/53.
—
ns-279.awsdns-34.com.
ns-582.awsdns-08.net.
ns-1270.awsdns-30.org.
ns-1576.awsdns-05.co.uk.
—
Anyone know how I might get this investigated?
on 20-03-2023 19:36
This is from a VM domestic connection.
Using nslookup hp.com <4x AWS R53 resolvers> each one very promptly replied & refused the query.
See below ...
on 20-03-2023 21:43
This is what I would expect to see, but I only receive timeouts for those servers.
on 21-03-2023 09:54
If it matters, we have a Hub 3 in Router mode & I'm using the default VM DNS via DHCP on my system.
The following lookups work for us and return IPs - perhaps for your system they also time out.
nslookup hp.com resolver1.opendns.com
nslookup hp.com dns.google
on 21-03-2023 16:13
on 23-03-2023 14:18
If I switch to my EE hotspot - I can resolve them fine. These resolver are part of Amazons R53 service and are publicly accessible.
This only seems to be an issue with my VM connection. Like packets are getting lost at the edge..
on 23-03-2023 14:19
on 23-03-2023 18:10
The Hub 5 in Router mode has been known to cause some DNS requests to time out.
on 28-03-2023 10:50
Do you have any further info on this? It would certainly fit my issue.
Thanks.
on 28-03-2023 14:09
It is a convoluted discussion over a couple of pages :
https://community.virginmedia.com/t5/Networking-and-WiFi/Timeout-resolving-DNS/td-p/5214111