I want to route a Route 53 domain to an EC2 instance.

The domain is


Here is the route53 console with A record: enter image description here

I have been following the article below. I simply create an "A" record and pointing it to the ip address of my ec2 instance. Is this all I need to do to start seeing my route53 domain pointed to my ec2 instance?

This is precisely what I have done in the past with Godaddy and works without issue. Am I missing an intermediate step? Do I need to create a traffic policy?

This domain was purchased on route53 so name servers are setup: ns-.awsdns-.com. ns-.awsdns-.net. ns-.awsdns-.co.uk. ns-.awsdns-.org.

I have been following this article: https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/routing-to-ec2-instance.html

  • Yes, that should be it. Give us the domain so we can take a look. – ceejayoz Jul 13 '18 at 19:11
  • Can you show us the Route53 console showing your records? – ceejayoz Jul 13 '18 at 19:48
  • @ceejayoz . I added a screenshot of the console. – petey Jul 13 '18 at 20:31

https://toolbox.googleapps.com/apps/dig/#A does not show an A record for operatica.io. NS setup looks good, but I guess that the A record is still missing

Route53 -> Hosted Zones -> operatica.io -> create record A type, add public EC2 ip.

| improve this answer | |
  • the tool shows "no error" and 899 IN SOA ns-1213.awsdns-23.org. awsdns-hostmaster.amazon.com. 1 7200 900 1209600 86400 . What part of the response shows there is no A Record? – petey Jul 13 '18 at 19:32
  • Its the fact that the ANSWER section is empty. Try to query anoter site and see the ANSWER part for comparision. – hargut Jul 13 '18 at 19:47
  • @petey The ANSWER section is empty. Try stackoverflow.com or fark.com or whatnot in that tool - you'll see one or more lines in the answer section. – ceejayoz Jul 13 '18 at 19:47
  • @hargut . I have attached the console to show the a record present. – petey Jul 13 '18 at 20:32

The nameservers you've configured for the domain are:


The nameservers Route53 told you (as shown in the screenshot) to configure for the domain are:


This is why your records aren't having any effect. Update your domain at your registrar to point at the correct set of nameservers. Every domain on Route53 has a potentially different random set of nameservers - you can't just copy them from another domain and have them work.

| improve this answer | |
  • I bought the domain on route53. You are saying they don't configure them or they are not pointing correctly? – petey Jul 13 '18 at 20:36
  • I don't buy domains on Route53, I just use their DNS, so I'm not sure. Maybe they set a default "parking" set of nameservers when you purchase. Either way, you need to update the domain to point at the right nameservers for the zone in the screenshot. – ceejayoz Jul 13 '18 at 20:39
  • Maybe you accidentally created a second zone for the same domain? docs.aws.amazon.com/Route53/latest/DeveloperGuide/… says "If you create records in a hosted zone other than the one that Route 53 creates automatically, you must update the name servers for the domain to use the name servers for the new hosted zone." – ceejayoz Jul 13 '18 at 20:39
  • 1
    Try to update the nameservers docs.aws.amazon.com/Route53/latest/DeveloperGuide/… – hargut Jul 13 '18 at 20:42
  • This is the first time i've bought on route53. I set the domain to the name servers you mentioned are "configured". I think that might work. – petey Jul 13 '18 at 20:43

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.