Discussion Locked

DNS not intergrating with AD

0 helpful
8 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I have been hearing that I should install DNS first and then AD. So I did that but now my new domain is not under Forward Lookup zone, so I manually added it but now I dont have the 4 folders _tcp, _msdn, etc.

How can I fix this or what is the right way to add your new AD to DNS afterward.

8 replies

by wburrows

There a couple of things you can do to check the environment. From the Domain Controller run the dcdiag resource kit utility. It generally points out any DNS issues in plain English. Once thing you did not mention was if the DNS server is dynamic. AD uses a dynamic DNS to write the srv records. Hope this helps.

by joseph moore

Here is some info on DNS and AD.

First, from Technet article 298143:

"SRV resource records: You must have a DNS server installed and configured for Active Directory and the associated client software to function correctly. Microsoft recommendsthat you use Microsoft DNS server, which is supplied with Windows 2000 Server as your DNS server. However, Microsoft DNS server is not required. The DNS server that you use must support the Service Resource Record (SRV RR) Requests for Comments (RFC) 2052, and the dynamic update protocol (RFC 2136). Use the DNS Manager Microsoft Management Console (MMC) snap-in to verify that the appropriate zones and resource records are created for each DNS zone. Active Directory creates its SRV RRs in the following folders:
_Msdcs/Dc/_Sites/Default-first-site-name/_Tcp
_Msdcs/Dc/_Tcp
In these locations, an SRV RR is displayed for the following services:
_kerberos
_ldap"

by shmaltz

You can just delete the DNS zones you have then creat a new DNS zone and make it interegrated with AD.

This discussion is closed to new replies.