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

My domain name is bound to AWS Global Accelerator but I'm not the owner of the Accelerator

0

Currently, I'm transferring my domain from Dreamhost to Godaddy. Once we transferred the domain correctly, we copied all my DNS zone records to the new hosting. Also, I moved my website to a new instance of WordPress Lightsail. I do not use the DNS zone in Lightsail, but I manage everything in GoDaddy. I create the A record in the DNS and point it to the static IP in my lightsail. However, I found that my domain is bound to an AWS Global Accelerator because when I do a DNS Lookup, we get 3 IPs (mine and the two from Accelerator), causing my website not to respond when I request the domain. We don't own and don't know who created the Accelerator. Is there a way to make this AWS Global Accelerator obsolete? I appreciate any help.

my domain is: seimdei.com (54.211.153.8)

https://dnschecker.org/all-dns-records-of-domain.php?query=www.seimdei.com&rtype=ALL&dns=cloudflare

Topics
Networking & Content DeliveryCompute
Tags
AWS Global AcceleratorAmazon LightsailNetworking & Content Delivery
Language
English
Daniel
asked 2 months ago218 views
1 Answer
2

Hi,

Is it possible that the NameServers for your domain with your domain registrar and the NameServer records provided by your DNS Hosting do not match completely?
i.e. the ANSWER section records shown when your run command dig NS seimdei.com should match the NameServers provided by your DNSHosting.

The site domain name loaded in the browser shows the Parked for free GoDaddy message. Which leads me to suspect above.

Another possibility is that the name-server update has not propagated fully which can take up to 48 hours.

I did find some GoDaddy documentation that mentions that they use AWS Global Accelerator internally in their architecture stack which could be the 2 additional IPs we are seeing due to the earlier mentioned NS records mismatch.

Thanks.

profile pictureAWS
EXPERT
AWS-SUM
answered 2 months ago
  • Daniel
    2 months ago

    Hello, and thank you for the response.

    For your first question, we are getting a match between NameServer from dig with the NameServer in the hosting (GoDaddy) ;; ANSWER SECTION: seimdei.com. 3278 IN NS ns58.domaincontrol.com. seimdei.com. 3278 IN NS ns57.domaincontrol.com.

    Regarding propagation, we updated the Apex record three days ago. We were expecting that propagation would be completed by today.

    I found that the other IPs are linked to a2aa9ff50de748dbe.awsglobalaccelerator.com This concerns me the most: I don't have any control over the URL belonging to the AWS global accelerator.

    Anyway, whatever leads you can give me would be appreciated.

  • AWS-SUM EXPERT
    a month ago

    When I run dig NS seimdei.com the ANSWER is different to the records you have posted above.

    ;; ANSWER SECTION:
seimdei.com.		3600	IN	NS	ns07.domaincontrol.com.
seimdei.com.		3600	IN	NS	ns08.domaincontrol.com.

    Please notice the ns07 and ns08 in place of ns57 and ns58 from yours and the difference in TTL of 3600 from 3278.

    So maybe check the NS match again :)

    If that is not it, then I would suggest reaching out to GoDaddy support, because I suspect those global accelerator IPs belong to some setup that GoDaddy has.

  • Daniel
    a month ago

    Yes, I just noticed that, too. Ultimately, as you said, it was a problem with the NS from GoDaddy. I moved the DNS zone and records to the Lightsail DNS zone and changed the NS to the ones from the Lightsail zone, and the problem is gone. Now, it is propagating correctly (no mysterious IP). Thanks for the leads! They gave some light.

  • AWS-SUM EXPERT
    a month ago

    Yayy, glad to see it worked out :)

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.

Guidelines for Answering Questions

Relevant content