Confused about issue with Win2K3 DNS
I am getting error 4515 complaining about DNS zones held in multiple partitions. I read this solution from Microsoft: http://support.microsoft.com/default.aspx?scid=kb;en-us;867464
that one points to this also:
http://support.microsoft.com/kb/817470/
Following what I believed to be what Microsoft says to do, I deleted the subdomain _msdcs.domain.com which was nested inside domain.com. I still have the domain _msdcs.domain.com. I did this from inside the DNS manager. No new problems (yet), but it didn't fix the old problem either. Finally after much reading, I have given up and I need clarification.
I have daily backups and if need be I could restore our 3 DCs (all running DNS) to their previous state. But I certainly hope that's not needed. I also moved up to Win2K3 Native since we have no Win2K or earlier servers at about the same time. These machines were built as Win2K3 DCs, not upgraded. Now, I'm not a Windows guy in the end. But I'm still responsible for this and I want to get it right so please bear with my newbieness and tell me what I need to do.
What is the relationship between what I see in adsiedit and in DNS manager? If I use adsiedit to clean up the domain, what exactly do I need to do? We only have one domain. In adsiedit, I see this:
ForestDSNZones
CN=Lost and Found
CN=MicrosoftDNS
DC=_msdcs.domain.com
CN=NTDS Quotas
DomainDNSZones
CN=Lost and Found
CN=MicrosoftDNS
DC=domain.com
DC=RootDNSServers
CN=NTDS Quotas
Under DNS Managers I see this under Forward Lookup Zones:
_msdcs.domain.com
dc
domains
gc
pdc
domain.com
_sites
_tcp
_udp
DomainDNSZones
ForestDNSZones
The last 2 have identical content. So, please help me understand what I am looking at and what I should do to make the error go away.
that one points to this also:
http://support.microsoft.com/kb/817470/
Following what I believed to be what Microsoft says to do, I deleted the subdomain _msdcs.domain.com which was nested inside domain.com. I still have the domain _msdcs.domain.com. I did this from inside the DNS manager. No new problems (yet), but it didn't fix the old problem either. Finally after much reading, I have given up and I need clarification.
I have daily backups and if need be I could restore our 3 DCs (all running DNS) to their previous state. But I certainly hope that's not needed. I also moved up to Win2K3 Native since we have no Win2K or earlier servers at about the same time. These machines were built as Win2K3 DCs, not upgraded. Now, I'm not a Windows guy in the end. But I'm still responsible for this and I want to get it right so please bear with my newbieness and tell me what I need to do.
What is the relationship between what I see in adsiedit and in DNS manager? If I use adsiedit to clean up the domain, what exactly do I need to do? We only have one domain. In adsiedit, I see this:
ForestDSNZones
CN=Lost and Found
CN=MicrosoftDNS
DC=_msdcs.domain.com
CN=NTDS Quotas
DomainDNSZones
CN=Lost and Found
CN=MicrosoftDNS
DC=domain.com
DC=RootDNSServers
CN=NTDS Quotas
Under DNS Managers I see this under Forward Lookup Zones:
_msdcs.domain.com
dc
domains
gc
pdc
domain.com
_sites
_tcp
_udp
DomainDNSZones
ForestDNSZones
The last 2 have identical content. So, please help me understand what I am looking at and what I should do to make the error go away.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Right click the domain.com zone (after it's expanded)
New Delegation.
The name is _msdcs
The FQDN of the server next screen is the FQDN of your DNS server.
New Delegation.
The name is _msdcs
The FQDN of the server next screen is the FQDN of your DNS server.
ASKER
It looks like it recreated it on it's own, but all 3 dns servers point to the one that they replicated from. Should I edit them so they all point to themselves?
If the zones are AD Integrated, then sure.
ASKER
Now all 3 servers are listed. I believe that's how it was originally so everything looks good. I'm going to wait until next week before I close this out just to make sure the problem doesn't return. But so far, so good! Thanks to both of you!
ASKER
Netman66, what exactly do you mean by recreating a referral record? Is that to fix what I deleted? If not, why? Can you give me a step-by-step please?