Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

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 am trying to implement a dynamic dns service for my computers. I have pointed to my EC2 instance in the NS record of and have installed dnsmasq on that system and have made sure to unblock the firewall port.

For now, I have statistically added an entry on my /etc/hosts file.

however, does not resolve correctly with nslookup or dig :-( This is the only time I could have this resolved (online nslookup) - is the IP address of the EC2 instance where dnsmasq is running. Where could I have gone wrong?

share|improve this question
The host i7 might be dead if my computer is off. – Lord Loh. Apr 6 '12 at 19:21
up vote 1 down vote accepted

Your NS record for is currently as follows:       1800    IN  NS

Which is wrong. NS records should specify not an IP addresses, but domain names of a nameservers, like this:       1800    IN  NS       1800    IN  A

or like this:       1800    IN  NS        1800    IN  A

Your DNS server at seems to work - it answers when I query of

share|improve this answer
Unfortunately, I still get IN NS 1800s (30m). I am expecting a different IP for is not the ip I set for in the hosts file :-( – Lord Loh. Apr 8 '12 at 21:27
Until you will read my answer, I can't help. – Sandman4 Apr 8 '12 at 23:32
Oh! I am sorry :-(. I think I read whatever was on my mind than what was on the screen :-( My shortcoming. When I query for, I get the right IP. I am still to figure out how to get the dnsmasq to resolve right. - Thank you. – Lord Loh. Apr 9 '12 at 16:15
Ughm, you still seem to read whatever it is on your mind :). DNSMASQ DOES RESOLVE RIGHT. Your DNS server at works OK. – Sandman4 Apr 9 '12 at 16:22
The "bad" record resides on, which is probably your DNS hosting or registrar. – Sandman4 Apr 9 '12 at 16:25

here is another tool but it is not resolving there.       1800    IN  NS       1800    IN  NS       1800    IN  NS

it resolves from my home now.

$ dig @

; <<>> DiG 9.7.3 <<>> @
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 17018
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0

;               IN      A

;; ANSWER SECTION:        0       IN      A

;; Query time: 111 msec
;; WHEN: Fri Apr  6 12:53:23 2012
;; MSG SIZE  rcvd: 49
share|improve this answer
I set the NS record for to – Lord Loh. Apr 6 '12 at 19:44
i tried web dig, and here is the result for the authoritative dns server which i have added to my answer. it seems that the dns server is indeed set up, so it has to be something within you instance or ec2. – johnshen64 Apr 6 '12 at 19:48
good news i have succeeded resolving it now. must be dns propagation. so it will take ttl time to propagate throughout internet (unless the dns servers that ignore ttl and cache records for longer). looks like your setup is correct. must be some sort of delay when i tested previously. sorry about that. – johnshen64 Apr 6 '12 at 19:54
Thanks! I think i'll wait and watch then :-) – Lord Loh. Apr 6 '12 at 20:03

Your Answer


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.