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

Route 53 Registered Domain Not Resolving

0

Hello,

I have searched far and wide and tried several of the proposed solutions to similar problems but I have had no luck.

I have an S3 Bucket that goes through CloudFront, I have linked this via a record set to my Route 53 Domain which was registered via Route 53.

If I test the record set using the test button on the AWS Console it says it is fine, however if you try and connect to the domain my browser gives DNS_PROBE_FINISHED_NXDOMAIN

My base domain is swiftthistle.co.uk with tag.swiftthistle.co.uk pointing to the cloud front distribution.

Any help would be great!

Tim

Edited by: timhasler on Mar 27, 2019 6:47 AM

asked 3 years ago48 views
2 Answers
0
Accepted Answer

Hi,

I can't confirm that your entire configuration is correct, but I did see that the NS record in the swiftthistle.co.uk hosted zone and the domain registration are both using the wrong name servers.

When you create a hosted zone, Route 53 assigns four name servers to that hosted zone. When you create another hosted zone, Route 53 assigns four different name servers to that hosted zone. Based on the current settings, I'd guess that you:
~ Deleted one hosted zone
~ Created another hosted zone
~ Changed the NS record in the new hosted zone to use the name servers from the domain registration, which has the name servers from the old hosted zone

Here's how you fix that:

  1. Get the name servers that Route 53 assigned to the new 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 in the new hosted zone 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

On a related note, you might also want to take a peek at "Getting Started," which explains how to use Route 53, S3, and CloudFront to distribute your content:

https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/getting-started.html

There are several versions of that explanation floating around in various docs; this is my favorite. :-)

Scott

EXPERT
answered 3 years ago
0

Hello Scott,

Thank you for you excellent and speedy answer! I think I did delete and remake the hosted zone at some point when I wasn't using the domain.

I'll assume this will work (Waiting on the name space change taking effect :) ) so I'll mark this as answered.

p.s. I think I saw your solution posted somewhere else but the instructions weren't clear, so thank you very much for making it understandable!

answered 3 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