DNS Resolution of RDS instances Timeout (External)
0
Im posting here as I have a couple of clients now reporting issues resolving RDS instances endpoint names when using Public DNS Servers such as 8.8.8.8 and also even using my local router.
I am curious if anyone else has started seeing this?
Language
English
1 Answer
- Newest
- Most votes
- Most comments
0
Hello.
I created RDS with my AWS account and tried to resolve the name using the "dig" command, and was able to successfully confirm the IP address.
The region I'm using is Tokyo.
It may be a good idea to check the domain propagation status on the following website.
https://www.nslookuptool.com/
dig database-1.yyyyyyy.ap-northeast-1.rds.amazonaws.com
; <<>> DiG 9.16.1-Ubuntu <<>> database-1.yyyyyyy.ap-northeast-1.rds.amazonaws.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 34240
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
;; QUESTION SECTION:
;database-1.yyyyyyy.ap-northeast-1.rds.amazonaws.com. IN A
;; ANSWER SECTION:
database-1.yyyyyyy.ap-northeast-1.rds.amazonaws.com. 5 IN A 172.31.17.149
;; Query time: 125 msec
;; SERVER: 192.168.11.1#53(192.168.11.1)
;; WHEN: 月 5月 13 22:22:12 JST 2024
;; MSG SIZE rcvd: 101
Relevant content
- Accepted Answer
asked 4 years ago 
AWS OFFICIALUpdated a year ago- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 13 days ago
- AWS OFFICIALUpdated 21 days ago
Thanks Riku..
Can you try dig database-1.yyyyyyy.ap-northeast-1.rds.amazonaws.com @8.8.8.8
Name resolution was also successfully performed using the dig command using 8.8.8.8.
Thanks, that was failing for me and other clients. Intrestingly, we found an outage in Germany related to Google AS# for the last 24 hours.. The DNS resolution for RDS is now working. Seems some underlying DNS/Routing issues from Google by the looks of it... Accepting the question for looking into the issue from your side.. Thanks Riku