AAAA Records Persisting for Domain Despite Not Being in Route 53 Configuration

If it is waiting on caching then it is a matter of time, however if you did not create the AAA records and therefore had nothing to delete, based on that here are some additional questions to answer: Could these records exist in a different hosted zone in your account or another account you manage? Are there other services that have created these records (Cloudfront, API Gateway or ELB) in your account or another account you manage?

Hi Riku_Kobayashi, I did not had any AAAA records before so I did not have nothing to delete. I am trying to confirm SSL certificate but it will not work baqsed on this problem.

The persistence of AAAA records that are not visible in your Route 53 hosted zone configuration could be due to several factors:

1. Caching: DNS records are often cached by various DNS servers and resolvers across the internet. Even after you've removed or updated records in Route 53, it can take some time (up to the TTL value) for these changes to propagate globally.

2. Multiple Hosted Zones: Check if you have multiple hosted zones for the same domain in Route 53. It's possible that the AAAA records exist in a different hosted zone that you're not currently viewing.

3. Nameserver Mismatch: Ensure that the nameservers listed in your domain registration settings exactly match those in your Route 53 hosted zone. A mismatch could lead to unexpected behavior.

4. External DNS Provider: Verify that you're not accidentally using another DNS provider alongside Route 53. Sometimes, domains can have lingering DNS settings from previous configurations.

5. TTL Values: Check the Time-to-Live (TTL) values on your existing records. Higher TTL values can cause changes to take longer to propagate.

To resolve this issue:

1. Double-check all hosted zones in Route 53 for your domain.
2. Verify your domain's nameserver settings in the Route 53 domain registration to ensure they match your hosted zone.
3. Use the dig or nslookup commands to query your domain's AAAA records directly from Route 53's nameservers. This will show you what Route 53 is actually serving.
4. If the records still persist, you may need to wait for the TTL to expire. You can temporarily lower TTL values on your existing records to speed up propagation of future changes.
5. If the issue continues after 48 hours, consider contacting AWS support for further assistance, as they can provide more in-depth troubleshooting for your specific case.

Remember, DNS changes can take up to 48 hours to fully propagate across the internet, so some patience may be required even after making corrections.
Sources
DNS Propagation Issues with Domain Registered in Route 53 - No Propagation After 48 Hours | AWS re:Post
CNAME Records not being found | AWS re:Post
Route 53 domain dns not propagating | AWS re:Post

did all of this... still have the isuue....

Hello.

I tried to resolve the AAAA record from my terminal, but it appears that the record has already been deleted.
I think the information you can see on the DNS checker site is probably delayed due to caching or something.
If you've already deleted it from the Route53 hosted zone, I think after a while it will no longer be possible to resolve the name from any DNS.

dig babypillars.com aaaa

; <<>> DiG 9.18.30-0ubuntu0.24.04.2-Ubuntu <<>> babypillars.com aaaa
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 31678
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
;; QUESTION SECTION:
;babypillars.com.               IN      AAAA

;; AUTHORITY SECTION:
babypillars.com.        900     IN      SOA     ns-1304.awsdns-35.org. awsdns-hostmaster.amazon.com. 1 7200 900 1209600 86400