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

If you go on and type in, the parent server tells me that nameservers for the domain are here:   ['']   [TTL=172800]   ['']   [TTL=172800]   ['']   [TTL=172800]   ['']   [TTL=172800] 

However, the zone file itself, which is authoritative, tells me that actually the nameservers are here instead:  ['']   [TTL=300]  ['']   [TTL=300]  ['']   [TTL=300] 

Can any one explain why would be listed as a nameserver when it isn't? What would happen if the resolver went to this address trying to find the A record for

share|improve this question is authoritative for; that is, it responds to a query with the aa flag set. If it were not authoritative, it would either be responding based on data cached based on other queries (which requires the aa flag be cleared), with a redirection toward the root servers (usually .) or with a query refusal. You can use dig as exemplified in my answer to your other question to see this for yourself. Try asking for and observe the difference (just don't overdo it). – Michael Kjörling Jul 26 '13 at 10:36
up vote 1 down vote accepted

Whoever registered the domain name provided 4 nameservers to the registrar, so the registrar have added 4 glue NS records for the domain with the relevant addresses.

For some reason, which only stackoverflow will know, only 3 nameservers have been added to the zone file. While ideally the nameservers listed on a domain's registration (as visible in whois) should match what's in the zone file, these 2 lists come from different places and so it's possible for them to be different.

It appears that ns4 does actually work so any requests going to that IP address will get a response.

share|improve this answer
Oddly enough, querying each of the four glue records for NS returns all four namesevers. I'm not sure why intodns would be reporting this. Assuming the SOA is accurate (yeah yeah I know), it was last updated on the 21st and the TTL is only 300. – Andrew B Jul 26 '13 at 15:04

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.