Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I got a static IP from EC2 and put it to A host part on godaddy to my domain. After that I defined 2 hosts ( and from godaddy with the same IP address. And put them into the nameserver field at my domain control panel. As you can understand rather than using name serves given by amazon, I want to create my own. It works with regular hosts but it didn't work with EC2. A week have past but the site is not directed. Can someone explain me what am I doing wrong?

share|improve this question
Can you please post the output of following commands: 1. netstat -npl | grep 53 2. telnet <hostname> 53 The second command should be run somewhere from outside the Amazon network. – GeekRide Dec 20 '12 at 11:24
You do what you want...but why not simply use Route53? About the only thing you can't do with it is to have it as a slave DNS. – Alex Dec 20 '12 at 16:33
What kind of nameserver daemon do you run on the instances? Are the security groups are set correctly (incoming UDP etc.)? Besides that: I'm pretty sure you don't want to mange your own nameservers. This is a pretty hard business due to the fact that the whole DNS is very compley in configuration. The fact that you want to use the same host with the same IP and try to set up these as two nameserver (which should/must reside in different class C networks) tell me that you seem to be not really aware of the whole complexity/difficulty about hosting nameservers. – Osterjour Dec 27 '14 at 21:52

Your Answer


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

Browse other questions tagged or ask your own question.