Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

I purchased a domain one week ago via nic.io. I have elected to provide my own DNS [because they provided no other option].

I'm trying to point my .io domain at my EC2 server instance. I've allocated an elastic IP and associated it with the instance. I can SSH into the instance and access point 80 via the IP address just fine. The IP is 54.235.201.241.

nic.io support said the following: "You have selected to provide your own DNS and therefore if there is an issue with the set-up of the name servers you will need to contact your DNS provider."

So, I created a Hosted Zone via Route 53 in AWS. This created NS and SOA records. I then set the Primary and Secondary servers at nic.io's domain admin page to the SOA record domains. Additionally, I set the optional servers to the NS domains. I did this two days ago, and I can't access the server via the domain.

I ran a DNS check here...still not sure what I need to do: http://mydnscheck.com/?domain=chadjohnson.io&ns1=&ns2=&ns3=&ns4=&ns5=&ns6=.

I have no idea what I'm supposed to do. Does anyone have any ideas?

share|improve this question

2 Answers 2

up vote 3 down vote accepted

That link gives you a few problems to work on:

cross T+0.51s WARNING: No address records returned for chadjohnson.io. Users who type http://chadjohnson.io/ into their web browser may not see your website

You need to create an A record in route 53 pointing chadjohnson.io to 54.235.201.241.

cross T+0.53s WARNING: No address records returned for www.chadjohnson.io. Users who type http://www.chadjohnson.io/ into their web browser may not see your website

You need to create an A record in route 53 pointing www.chadjohnson.io to 54.235.201.241.

information T+0.53s Performing email checks cross T+0.54s WARNING: no MX records returned for CHADJOHNSON.IO

You need to create an MX record in route 53 pointing MX to chadjohnson.io, choose priority 10.

cross T+0.54s Diagnosis completed with errors

After you do these steps, you should be able to:

ssh chadjohnson.io and connect to your ec2 node.

Enter http://chadjohnson.io into a browser and connect to your website.

share|improve this answer
    
Thanks. I missed that once you create a hosted zone, you can then create record sets within that hosted zone. Personally, I think the Route 53 user interface could be better. –  Chad Johnson Nov 9 '13 at 1:27
    
The interface is terrible but then again so are all of the DNS web UI's. –  dmourati Nov 9 '13 at 3:39

I then set the Primary and Secondary servers at nic.io's domain admin page to the SOA record domains. Additionally, I set the optional servers to the NS domains

ok, so looks like you did this right

$ dig chadjohnson.io ns +short
ns-1031.awsdns-00.org.
ns-2014.awsdns-59.co.uk.
ns-780.awsdns-33.net.
ns-187.awsdns-23.com.

so now just log into route53, and add the missing A record (to be the same as your server IP), and you're good...

missing A record:

$ dig chadjohnson.io a +short
$ dig www.chadjohnson.io a +short
$

share|improve this answer
    
Thanks. I'd mark this as the answer, but someone got to it before you :) I've upvoted your answer. –  Chad Johnson Nov 9 '13 at 1:27

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

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