Showing results for 
Search instead for 
Did you mean: 

Issues querying certain R53 resolvers

Tuning in

I’m having issues obtaining a DNS response from four AWS R53 resolvers.

I receive timeouts when querying over UDP/53.


Anyone know how I might get this investigated?



This is from a VM domestic connection.

Using nslookup <4x AWS R53 resolvers> each one very promptly replied & refused the query.

See below ...



This is what I would expect to see, but I only receive timeouts for those servers.

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.



I suspect that the AWS R53 resolvers can only be used by those who have the necessary login.

Hub 5, TP-Link TL-SG108S 8-port gigabit switch, 360
My Broadband Ping - Roger's VM hub 5 broadband connection

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..

am able to resolve all domains without issue:

MacBook-Pro:tmp username$ dig +short

The Hub 5 in Router mode has been known to cause some DNS requests to time out.

Do you have any further info on this? It would certainly fit my issue.