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 got Linux DNS server running years ago, and we're trying to add an Active Directory server on the network.

The AD is congigured to have static IP, and a DNS A record pointed to it.


Now, as I try to join a client to it, it fails. If I use the domain name, xxxx...., it will fail completly, as it says it can't find the controller to it. If I use the NetBIOS name, I get a prompt to input my account information, but then failed.

How to fix this?

share|improve this question
up vote 2 down vote accepted

AD does not get a static IP address. Do you mean that your (presumably singular) domain controller has a static IP? It's not enough to create an A record for this, as AD requires many SRV (and other) records to function properly. While it is possible to manually create all of the needed entries, it is not a tenable solution in the long-term.

In lieu of creating manual static DNS entries, you want to create a subdomain (say for your AD, and delegate control over that to your Windows DNS servers. This will permit AD to manage its own DNS namespace, creating and modifying the records it needs without you needing to muck about with manually changing things all the time.

For more information on AD and DNS (and many other crucial AD-related topics), please see MDMarra's spectacular Active Directory Q&A:

share|improve this answer
I got it, I think I am best off to create a subdomain for it. – Shane Hsu Feb 4 '13 at 5: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.