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

have a server 2003 domain controller i have installed active directory integrated dns

under the forward lookup zone for domain_name.local i see an APIPA ip address that is set for (same as parent folder) with ip number 169.x.x.x

looks like (same as parent folder) Host A 169.x.x.x (apipa subnet range)

problem is, from other forums that i have read, that this is due to dual nics and one on that is not getting a dynamic or static ip address BUT... I only have one nic in this server?

where could this be coming from and could it mess up other settings or not allowing the DC to be contacted? i am just wondering what symptoms could arise due to the record being there.

any help would be greatly appreciated thanks.

share|improve this question
up vote 0 down vote accepted

Could you have a NIC on the server that has (or maybe did have, this may not be something that is updated when you load AD/netlogon on a DC)?

If you have another DNS server in your environment you could 'try' creating a primary zone (not AD Integrated) and pointing a DC at it and restart the netlogon service. This should recreate the core AD zone and you can see if you have resolved the issue. Do this at your own risk! (see

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.