In my DNS tree, the _MSDCS folder is delegated (greyed out).
Is this correct? as my DNS server is my DC.
Main Topics
Browse All TopicsHello all,
PROBLEM:
I have an error log absolutly jam-packed with error code 7062's.
INFRASTRUCTURE:
I have a Windows 2003 Server Native domain with 1 domain controller and WinXP Pro clients. Within the same building there is another seperate domain with 1 Windows 2003 server DC. There is a 1-way trust between the domains. My DNS tree has forward lookup zones for both domains.
SYMPTOMS:
The 7062 error contains this info:
--------------------------
Event Type: Warning
Event Source: DNS
Event Category: None
Event ID: 7062
Date: 12/01/2007
Time: 14:27:52
User: N/A
Computer: PDC2
Description:
The DNS server encountered a packet addressed to itself on IP address 10.16.1.234. The packet is for the DNS name "_ldap._tcp.PARK-HIGH._sit
Check the following areas for possible self-send configuration errors:
1) Forwarders list. (DNS servers should not forward to themselves).
2) Master lists of secondary zones.
3) Notify lists of primary zones.
4) Delegations of subzones. Must not contain NS record for this DNS server unless subzone is also on this server.
5) Root hints.
Example of self-delegation:
-> This DNS server dns1.example.microsoft.com
-> The example.microsoft.com zone contains a delegation of bar.example.microsoft.com to dns1.example.microsoft.com
(bar.example.microsoft.com
-> BUT the bar.example.microsoft.com zone is NOT on this server.
Note, you should make this delegation check (with nslookup or DNS manager) both on this DNS server and on the server(s) you delegated the subzone to. It is possible that the delegation was done correctly, but that the primary DNS for the subzone, has any incorrect NS record pointing back at this server. If this incorrect NS record is cached at this server, then the self-send could result. If found, the subzone DNS server admin should remove the offending NS record.
You can use the DNS server debug logging facility to track down the cause of this problem.
For more information, see Help and Support Center at http://go.microsoft.com/fw
Data:
0000: 50 25 00 00 P%..
--------------------------
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
Hi,
If it's Delegated it should also have some NS Records underneath it ("(Same as Parent Folder)" Name Server <NameServerIP>). Where do those point to?
If it's your local server, do you have a Forward Lookup Zone called _msdcs.park-high.local (in addition to your Park-High.local zone)?
If not, add a new Forward Lookup Zone called _msdcs.park-high.local. Make it Active Directory Integrated and set it to Replicate to all DCs in the Domain (or Forest). Ensure that Dynamic Updates is set to Secure Only.
Once done run these commands on your DCs:
net stop Netlogon
net start Netlogon
ipconfig /registerdns
HTH
Chris
Hi,
Look at this:
http://support.microsoft.c
And perhaps also restore your original root servers like this:
http://support.microsoft.c
Regards,
Johan
>>If you don't want to maintain that as a seperate zone simply delete the greyed out _msdcs folder from your main Forward Lookup Zone, check Dynamic Updates is on then run the >>commands above and ensure it's appeared.
This seemed to work perfectly. I will wait a few minutes for any errors to report and then get back to you.
Do you know why the _msdcs folder may have become delegated without any (apparent) administrator intervention?
Thanks...
Business Accounts
Answer for Membership
by: bgcm12Posted on 2007-01-12 at 07:42:57ID: 18302192
Dcdiag gives this info:
---------- ---------- ---------- ---------- ---------- ---------- ---------- ---------- ---------- -
65355adc37 ._msdcs.Pa rk-High.lo cal co 565355adc3 7._msdcs.P ark-High.l ocal) couldn't
---------- ---------- ---------- ---------- ---------- ---------- ---------- ----------
--------------------------
Performing initial setup:
Done gathering initial info.
Doing initial required tests
Testing server: Park-High\PDC2
Starting test: Connectivity
The host 01eb85ee-1a2e-4c48-8962-75
uld not be resolved to an
IP address. Check the DNS server, DHCP, server name, etc
Although the Guid DNS name
(01eb85ee-1a2e-4c48-8962-7
be resolved, the server name (pdc2.Park-High.local) resolved to the IP
address (10.16.1.234) and was pingable. Check that the IP address is
registered correctly with the DNS server.
......................... PDC2 failed test Connectivity
Doing primary tests
Testing server: Park-High\PDC2
Skipping all tests, because server PDC2 is
not responding to directory service requests
Running partition tests on : TAPI3Directory
Starting test: CrossRefValidation
......................... TAPI3Directory passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... TAPI3Directory passed test CheckSDRefDom
Running partition tests on : ForestDnsZones
Starting test: CrossRefValidation
......................... ForestDnsZones passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... ForestDnsZones passed test CheckSDRefDom
Running partition tests on : DomainDnsZones
Starting test: CrossRefValidation
......................... DomainDnsZones passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... DomainDnsZones passed test CheckSDRefDom
Running partition tests on : Schema
Starting test: CrossRefValidation
......................... Schema passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... Schema passed test CheckSDRefDom
Running partition tests on : Configuration
Starting test: CrossRefValidation
--------------------------