DNS A record not resolving to EC2 external IP

0

Our hosted zone A record somehow does not resolve anymore to the EC2 external IP it is configured for. It was working a few days back, then we got some errors so it was decided to recreate the A record. Once created, it does not resolve anymore. Using the default http://ec2 uRL still works and we are left with using that for the moment

asked 5 years ago298 views
8 Answers
0

delete 

Edited by: oibsurfer on Oct 13, 2019 3:39 PM

Edited by: oibsurfer on Oct 13, 2019 3:39 PM

answered 5 years ago
0

Any help would be greatly appreciated. I tried to delete the record set for the www alias, even deleted and recreated the whole hosted zone to no avail

answered 5 years ago
0

Hi,

I can take a look at your configuration. What's the name of the domain?

Scott

EXPERT
answered 5 years ago
0

Hi Scott

Sent you a PM

answered 5 years ago
0

Hi,

In general, name servers are supposed to be the same in three places:
~ The name servers that Route 53 assigned to your hosted zone when you created it. These name servers can't be changed.
~ The name servers in the NS record for the hosted zone. By default, these name servers match the name servers that Route 53 assigned to the hosted zone. You can edit them, but usually you don't need to.
~ The name servers that are associated with your domain registration. These name servers control which hosted zone is used to route traffic for your domain.

In this case, the name servers in the NS record and the name servers for the domain registration don't match the name servers that Route 53 assigned to the hosted zone. I'd guess that you had another hosted zone at some point, you deleted it, and you created a new hosted zone. When you create a new hosted zone, Route 53 assigns four new name servers to the new hosted zone.

Here's how you get everything up and running again:

  1. Get the name servers that Route 53 assigned to the hosted zone. See "Getting the Name Servers for a Public Hosted Zone" in the Route 53 Developer Guide:

https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/GetInfoAboutHostedZone.html

  1. Update the NS record to use the name servers that you got in step 1. See "Editing Records":

https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/resource-record-sets-editing.html

  1. Update the domain registration to use the name servers that you got in step 1. See "Adding or Changing Name Servers and Glue Records for a Domain":

https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/domain-name-servers-glue-records.html

Some DNS resolvers have cached the current name servers, and the default cache duration (TTL) is two days, so it'll be a while before you'll be able to access your website yourself.

Scott

EXPERT
answered 5 years ago
0

Thanks for the reply Scott!

Does the servers in the NS entry have to be in the same order as those defined for the domain registration? I also noticed that for the SOA entry there's one name server included in the setting. Can i set it to any of the name servers, or does it have to be a specific one?

answered 5 years ago
0

Hi,

You can specify the name servers in any order.

The SOA record isn't involved in DNS resolution, so the name of the Route 53 name server that appears in that record doesn't matter. You don't need to change it.

Scott

EXPERT
answered 5 years ago
0

Thanks for your assistance Scott! Finally have the URL internet accessible.

answered 5 years ago

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