Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations wOOdy-Soft on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Issue with DNS within AD 1

Status
Not open for further replies.

r8j8t

IS-IT--Management
May 11, 2007
51
GB
Hello
I am bit new to win2003 server and DNS.
The problem I am facing is bit strange:
I am having a Win2003R2 server. I DC promo it to make it first DC of new forest test.co.uk. There is no DNS server running on the server so I let AD add and configure my DNS also.
After the server becomes DC of test.co.uk domain, I checked the zones in DNS. To my surprise there are two forward loking zones one is test.co.k and other _msdc.test.co.uk.
As far as I know this _msdc is SRV record.
There is also an _msdc srv recored which only holds ns recored type.
The other records which _msdc should be containing is under forward looking zone _msdc.test.co.uk(_gc,SOA,Cname etc)

I checked DNS log but could only find a warning saying "DNS server could not get zone info from AD. It may be due to heavy load". But this a newly buil server and is 1st DC for the new forest.
Also when i ran nslookup i get respond that "could not find server for 191.x.x.x. The deafult server cannot be found".
I checked directory services,FRS logs but there was no error.
I have also checked the services like netlogon,frs etc are running successfully or not.
I even tried restarting netlogon service. I ran a test on dns for simple dns querry and it was successfull.

If someone can help me solve this puzzle i will be very gratefull...
 
Ok here goes..

the _msdc zone is created by default as a seperate zone since Microsoft is trying to prepare your dns for any future growth, I could have been placed within your test.co.k zone but since best practice is to delegate this zone to your other forward lookups that is why it gets its own special place in DNS (read up on the "whys" for this on technet as it is a bit long winded). Indeed this zone does contain SRV records that are critical to AD and if this zone had not been created at all you would have some serious problems ;)

The reason your nslookup returned an unexpected result is from the fact that you are lacking a reverse lookup zone for this ip range. It queries these zones to do IP to name resolution.

Hope this helps.

Cory
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top