Route 53 dns's record doesn't work, how to solve
0
Set a route 53 dns record, but doesn't work. Visited from Vietnam and Japan, all met DNS_PROBE_FINISHED_NXDOMAIN error.
Route 53 dns record detail:
2 Answers
- Newest
- Most votes
- Most comments
1
Hello.
I am accessing the website from my PC (Tokyo) and am able to access the website normally.
Also, I think the domain settings are correct because the IPv6 address can be resolved using the AAAA record as shown below.
dig could.ai aaaa
; <<>> DiG 9.16.1-Ubuntu <<>> could.ai aaaa
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 12356
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;could.ai. IN AAAA
;; ANSWER SECTION:
could.ai. 60 IN AAAA 2406:da18:0:4f6b:1b2e:37e4:e521:c6c0
could.ai. 60 IN AAAA 2406:da18:961:1d8f:aeec:67eb:1a87:82f7
;; Query time: 39 msec
;; SERVER: 192.168.11.1#53(192.168.11.1)
;; WHEN: 水 9月 18 22:49:11 JST 2024
;; MSG SIZE rcvd: 93
I think there is probably a problem with your local environment.
1
You've set AAAA record which results to IPv6 addresses.
~ ❯ dig aaaa could.ai +short
2406:da18:0:4f6b:1b2e:37e4:e521:c6c0
2406:da18:961:1d8f:aeec:67eb:1a87:82f7
Looks like your browser is running on an IPv4 network so it automatically tries to perform an A record resolution to receive an IPv4 address but you have not set any, hence the NXDOMAIN result.
Relevant content
asked a year ago
asked 2 years ago
asked 4 years ago
Google's DNS server can resolve names, so why not temporarily change the DNS server your PC is referring to to something like "8.8.8.8"? By the way, does your ISP support IPv6? Please note that if it does not support IPv6, you will not be able to access it.