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

We have a problem where we cannot access one of our user areas created on an internal server. We have found that it is an issue with the interrogation of the nameserver as the nameserver itself is working. The virtual dns is working and active and the domains are running but when we try and ping this internal address it comes back as unknown host when we can ping other internal directories without problem.

share|improve this question
What operating system? – RedGrittyBrick Nov 15 '10 at 18:06
Sorry, forgot to mention. This is on linux, debian 2.6.30-6. – Jon Nov 16 '10 at 9:02

That sounds like an issue with access control or the zone just not loading. Normally on a public-facing nameserver you would have a set of ACLs defining who can view or use what content.

For example you may have one allowing the localhost to do recursive lookups (lookup anything), another allowing localhost and local hosts to lookup your internal-only DNS records and a final global one just allowing external hosts to lookup domains which you are the authoritative external server for.

My guess would be somehow the definition for that specific zone has the wrong ACLs applied (maybe in the wrong section of your config) or is not loading.

Check it's being loaded ok on the nameserver by looking at the logs and check if you can resolve it from the nameserver itself (usually as I mentioned allowed to resolve anything on the nameserver).

This should point you in the right direction.

share|improve this answer

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.