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

DOMAIN NAME NOT REFLECTING HOSTED ON ROUTE 53

0

i HAVE REGISTERED MY DOMAIN ON AWS AND ALSO MAPPEND EIP WITH THE FORWARD RECORD 'A', WHEN I TYPE EIP IT WORKS ON BROWSER INSTEAD OF WHEN I TYPE MY DOMAIN NAME . RECORD A AND PTR NOT REFLECTING WHEN CHECKED ON DNS PROPAGATION SITE. BUT ON USING DIG COMMAND IT ANSWER PTR AND A QUERY... PLEASE HELP ME IN THIS REGARD.

1 Answers
0

Hello rePost-User-7580137,

When you are using the dig command, what DNS servers are you querying?

It sounds like there may be a name server (NS) mismatch between the domain registrar and your hosted zone.

Please try the following:

  1. Get the name servers for a public hosted zone.
  2. Search for your website's domain name using your preferred WHOIS utility (domain registration lookup tool).
  3. Verify if the NS for your domain in the WHOIS output matches the same NS records in your Route 53 public hosted zone.
  4. If the NS records don't match and your domain registrar is Route 53, then update the name servers for your domain at the registrar to the four authoritative NS records assigned to your Route 53 public hosted zone. Note: For domains registered with third-party registrars, follow your registrar's documentation to change the domain's NS.

Note: It might take until the TTL (up to 48 hours) for the previous registrar's NS to expire from the top-level domain (TLD). During this period, DNS queries for the domain might be sent to both Route 53 and the prior registrar's NS. Route 53 immediately responds to DNS queries for the domain from resolvers that haven't cached the prior registrar's NS.

Here is a troubleshooting article if the above does not resolve your issue.

I hope this information is helpful.

profile picture
answered a month ago
  • Thanks Nick ! In fact i had check these parameters before sharing my query. Here is the NS details maintained with registrar which is AWS 53 AND dig command output Restrar NS servers ns-2028.awsdns-61.co.uk ns-917.awsdns-50.net ns-164.awsdns-20.com ns-1500.awsdns-59.org ns-578.awsdns-08.net ns-1427.awsdns-50.org

    ns-578.awsdns-08.net. ns-1427.awsdns-50.org. ns-475.awsdns-59.com. ns-1927.awsdns-48.co.uk. ns-2028.awsdns-61.co.uk ns-917.awsdns-50.net ns-164.awsdns-20.com

    dig output globalservices.com. 3600 IN NS ns-475.awsdns-59.com. globalservices.com. 3600 IN NS ns-578.awsdns-08.net. globalservices.com. 3600 IN NS ns-917.awsdns-50.net. globalservices.com. 3600 IN NS ns-1427.awsdns-50.org. globalservices.com. 3600 IN NS ns-164.awsdns-20.com. globalservices.com. 3600 IN NS ns-1927.awsdns-48.co.uk. globalservices.com. 3600 IN NS ns-2028.awsdns-61.co.uk.

    The NS servers are almost same as per the registrar NS list.

    regards Pritam

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