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'm getting a problem resolving a domain when their ns servers don't have an A record.

I'm running bind 9.3.2P2.

For example

when trying from Windows dns servers it seems to work fine.


share|improve this question
Are you using the same DNS servers in both cases or does BIND uses the root servers (the default config) and Windows the servers provided by your ISP? – Cristian Ciupitu Sep 15 '09 at 9:22

If the NS server don't have an A record how can BIND find out their IP address in order to query them? It can't, so it can't resolve domains served by them.

On a side note I've run a test myself and I've noticed that I can resolve using the DNS servers of my ISP, but I can't by running dig +verbose (this uses the root name servers). Your issue is caused by an improperly configured domain. My guess would be that the DNS servers of my and your ISP have the address of in their cache, while the current setup of the domain is incorrect.

share|improve this answer

Your Answer


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