ABiffel

Servus, hatte einen Kunden bei dem nach einer Migration von AD W2000 aud AD W2003 alle 5 Minuten folgender Fehler im DNS LOG hatte: The DNS server encountered error 9002 attempting to load zone . from Active Directory. The DNS server will attempt to load this zone again on the next timeout ... Die Zone "." gab es nicht, auch keine anderst geartete ROOT Zone. Folgende Lösung empfohl mir der Microsoft Support: C:\>ntdsutil ntdsutil: domain management domain management: connections server connections: connect to server local host Binding to local host ... Connected to localhost using credentials of locally logged on user. server connections: quit domain management: list Note: Directory partition names with International/Unicode characters will only display correctly if appropriate fonts and language support are loaded Found 6 Naming Context(s) 0 - CN=Configuration,,DC=Domain,DC=intra 1 - DC=Domain,DC=intra 2 - CN=Schema,CN=Configuration,DC=Domain,DC=intra 3 - DC=ForestDnsZones,DC=Domain,DC=intra 4 - DC=DomainDnsZones,DC=Domain,DC=intra domain management: delete nc DC=DomainDnsZones,DC=Domain,DC=intra domain management: delete nc DC=ForestDnsZones,DC=Domain,DC=intra The operation was successful. The partition has been marked for removal from the enterprise. It will be removed over time in the background. Note: Please do not create another partition with the same name until the servers which hold this partition have had an opportunity to remove it. This will occur when knowledge of the deletion of this partition has replicated throughout the forest, and the servers which held the partition have removed all the objects within that partition. Complete removal of the partition can be verified by consulting the Directory event log on each server. domain management:quit The DomainDNSzones partition was removed from the Active directory. 4. Then we restarted the necessary services and registered the server in DNS: net stop dns net stop netlogon ipconfig/flushdns net start dns net start netlogon ipconfig/registerdns Der Fehler ist bei Microsoft bekannt, die Ursache allerdings nicht. Ich hoffe es hilft euch weiter ....

Servus, hatte einen Kunden bei dem nach einer Migration von AD W2000 aud AD W2003 alle 5 Minuten folgender Fehler im DNS LOG hatte: The DNS server encountered error 9002 attempting to load zone . from Active Directory. The DNS server will attempt to load this zone again on the next timeout ... Die Zone "." gab es nicht, auch keine anderst geartete ROOT Zone. Folgende Lösung empfohl mir der Microsoft Support: C:\>ntdsutil ntdsutil: domain management domain management: connections server connections: connect to server local host Binding to local host ... Connected to localhost using credentials of locally logged on user. server connections: quit domain management: list Note: Directory partition names with International/Unicode characters will only display correctly if appropriate fonts and language support are loaded Found 6 Naming Context(s) 0 - CN=Configuration,,DC=Domain,DC=intra 1 - DC=Domain,DC=intra 2 - CN=Schema,CN=Configuration,DC=Domain,DC=intra 3 - DC=ForestDnsZones,DC=Domain,DC=intra 4 - DC=DomainDnsZones,DC=Domain,DC=intra domain management: delete nc DC=DomainDnsZones,DC=Domain,DC=intra domain management: delete nc DC=ForestDnsZones,DC=Domain,DC=intra The operation was successful. The partition has been marked for removal from the enterprise. It will be removed over time in the background. Note: Please do not create another partition with the same name until the servers which hold this partition have had an opportunity to remove it. This will occur when knowledge of the deletion of this partition has replicated throughout the forest, and the servers which held the partition have removed all the objects within that partition. Complete removal of the partition can be verified by consulting the Directory event log on each server. domain management:quit The DomainDNSzones partition was removed from the Active directory. 4. Then we restarted the necessary services and registered the server in DNS: net stop dns net stop netlogon ipconfig/flushdns net start dns net start netlogon ipconfig/registerdns Der Fehler ist bei Microsoft bekannt, die Ursache allerdings nicht. Ich hoffe es hilft euch weiter ....