Skip to content
By using AWS re:Post, you agree to the AWS re:Post Terms of Use
AWS re:Postre:Post
About re:Post

domain algnotes.info registered with AWS Route 53 stopped resolving after automatic renewal

0

My domain algnotes.info has stopped resolving. For example:

; <<>> DiG 9.10.6 <<>> algnotes.info @8.8.8.8
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 28295
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;algnotes.info.			IN	A

;; AUTHORITY SECTION:
info.			1800	IN	SOA	a0.info.afilias-nst.info. hostmaster.donuts.email. 1733535470 7200 900 1209600 3600

;; Query time: 72 msec
;; SERVER: 8.8.8.8#53(8.8.8.8)
;; WHEN: Fri Dec 06 20:50:02 EST 2024
;; MSG SIZE  rcvd: 121

Also, https://registrar.amazon.com/whois?domain=algnotes.info returns `No match for "algnotes.info" in the registrar database.'

The domain is hosted by AWS Route 53. The same AWS name servers that are listed for it in the Route 53 (public) hosted zone for the domain are listed in the Route 53 registered domain details for the domain. If I query one of these name servers I do get the correct resolution:

> dig algnotes.info @ns-1731.awsdns-24.co.uk                                                                                                                                                       [20:56:14]

; <<>> DiG 9.10.6 <<>> algnotes.info @ns-1731.awsdns-24.co.uk
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 29605
;; flags: qr aa rd; QUERY: 1, ANSWER: 1, AUTHORITY: 4, ADDITIONAL: 1
;; WARNING: recursion requested but not available

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;algnotes.info.			IN	A

;; ANSWER SECTION:
algnotes.info.		3600	IN	A	3.231.125.220

;; AUTHORITY SECTION:
algnotes.info.		172800	IN	NS	ns-118.awsdns-14.com.
algnotes.info.		172800	IN	NS	ns-1189.awsdns-20.org.
algnotes.info.		172800	IN	NS	ns-1731.awsdns-24.co.uk.
algnotes.info.		172800	IN	NS	ns-979.awsdns-58.net.

;; Query time: 21 msec
;; SERVER: 2600:9000:5306:c300::1#53(2600:9000:5306:c300::1)
;; WHEN: Fri Dec 06 20:56:40 EST 2024
;; MSG SIZE  rcvd: 198

But the top-level .info resolvers don't seem to know that these are the authoritative name servers:

> dig algnotes.info @a0.info.afilias-nst.info                                                                                                                                                      [20:58:16]

; <<>> DiG 9.10.6 <<>> algnotes.info @a0.info.afilias-nst.info
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 2730
;; flags: qr aa rd; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1
;; WARNING: recursion requested but not available

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
;; QUESTION SECTION:
;algnotes.info.			IN	A

;; AUTHORITY SECTION:
info.			3600	IN	SOA	a0.info.afilias-nst.info. hostmaster.donuts.email. 1733536104 7200 900 1209600 3600

;; Query time: 95 msec
;; SERVER: 2001:500:19::1#53(2001:500:19::1)
;; WHEN: Fri Dec 06 21:02:47 EST 2024
;; MSG SIZE  rcvd: 121

The problem seems to have started when Route 53 automatically renewed the domain a few days ago. Other than that, nothing has changed recently.

I opened a support ticket with AWS two days ago, but my support level is only basic, and I've gotten no response yet.

I notice that the contact info listed for it in the registered domain section is correct, and up to date, but shows a red "expired" flag. Perhaps that's the problem? The contact info is up to date, and I've edited and resaved it, but it still shows the "expired" flag.

Can somebody help me fix this? That is, get the domain to properly resolve again?

Thank you for any help.

Topics
Networking & Content Delivery
Tags
Amazon Route 53Domain Name System (DNS)Route 53 Registrar
Language
English
asked a year ago71 views
2 Answers
2
Accepted Answer

Changing and saving the contact info for the domain resolved the issue.

answered a year ago
EXPERT
reviewed a year ago
EXPERT
reviewed a year ago
2

Based on the information provided, it appears that your domain algnotes.info is experiencing issues with its DNS configuration after an automatic renewal through Amazon Route 53. This situation is indicative of a problem where the domain's name servers are not properly registered or propagated at the registry level. Here are some steps you can take to troubleshoot and potentially resolve the issue:

  1. Verify domain registration status: Check if the domain is still properly registered with Route 53. Sometimes, automatic renewals can fail due to payment issues or other technical problems.

  2. Confirm name server settings: Double-check that the name servers listed in your Route 53 hosted zone match exactly with those in the domain's registration details.

  3. Re-push name servers: Try updating the name servers for your domain in Route 53, even if they're the same. This action can sometimes trigger a re-push of the information to the registry.

  4. Check for domain suspension: Ensure that your domain hasn't been suspended due to any verification issues or policy violations.

  5. Verify WHOIS information: Make sure all the WHOIS information for your domain is up to date and accurate.

  6. Contact AWS support: Although you've already opened a ticket, try to escalate the issue if possible. Explain that your domain is not resolving globally due to a problem with the registry-level name servers after an automatic renewal.

  7. Consider manual intervention: In some cases, you may need to manually update the name servers at the registry level. This typically requires contacting the domain registrar (in this case, AWS) to perform this action on your behalf.

  8. Be patient: DNS changes can take up to 48 hours to propagate fully, although they often happen much faster.

If these steps don't resolve the issue, and AWS support doesn't respond in a timely manner, you may need to consider upgrading your support plan temporarily to get more immediate assistance, as this is a critical issue affecting your domain's availability.

Remember that only AWS can directly intervene with the .info registry to ensure your domain's name servers are correctly set at the registry level. Continue to follow up on your support ticket and provide them with all the relevant information you've gathered about the issue.
Sources
Troubleshooting Amazon Route 53 - Amazon Route 53
.info - Amazon Route 53

answered a year ago
EXPERT
reviewed a year ago
  • NY
    a year ago

    1. Route 53 did charge the recent domain renewal to my credit card, so there was no payment issue. The domain name is listed in the "Registered domains" section of Route 53 dashboard, so I think it is indeed registered.

    2. Yes, they match.

    3. I've tried that.

    4. I don't know how to check for a domain suspension.

    5. The whois information that Route 53 dashboard shows is correct, although it has a red "expired" flag that I cannot seem to get rid of. I don't know why that is there. The contact info is up to date. I tried editing and resaving the contact info, but it still says "expired".

    6. I opened a ticket, but don't seem to be able to escalate it on the basic plan. I have explained the problem as suggested.

    7. Well, okay, how do I contact AWS to ask them to perform this action?

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Relevant content