DNS doesn't resolve

Hi,

The hosted zone for 6beagles.com is a private hosted zone rather than a public hosted zone. To update your configuration, perform the following steps:

1. Create a public hosted zone for 6beagles.com. See "Creating a public hosted zone" in the Route 53 Developer Guide:

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

2. Create your records in the new hosted zone. See "Creating records by using the Amazon Route 53 console":

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

3. Get the name servers that Route 53 assigned to the new hosted zone. See "Getting the name servers for a public hosted zone":

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

4. Update your domain registration to use the new name servers. 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 topic, I tried to use the domain name that's assigned to your load balancer to see if your website is working, and I got a 502 error (bad gateway). You will need to fix that, too, before DNS can route traffic to your website.

Scott

Thanks for the reply.

I was creating HostedZone using CF template, and I found that having VPC properties make HostedZone private.
Once I removed this property from CF template and recreated, I can see the new HostedZone of type Public, but still the DNS fails to resolve.

Any idea? Thanks.

Hi,

Your DNS configuration is now correct. It will take a couple of days for you to be able to see your website again because DNS resolvers typically cache the names of name servers for two days. (Folks who use different DNS resolvers will be able to see your website as soon as you make the change. You might also be able to see your website from your phone.) For an overview of how DNS works, including the part about resolver caching, see "How Amazon Route 53 routes traffic for your domain":

https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/welcome-dns-service.html#welcome-dns-service-how-route-53-routes-traffic

I'm still seeing a 502 error (bad gateway) on your application load balancer when I try to access it using the DNS name for the load balancer, mds-alb-130... Even when resolver caching expires and DNS starts using the new name servers, you won't be able to access your website until that is fixed.

Scott

Scott