Estou recebendo esses dois erros no log de eventos DNS (erros no final da pergunta). Eu confirmei que tenho zonas duplicadas. Eu estou querendo saber quais excluir. O DomainDNSZone contém todos os nossos registros DNS, mas não tem a zona _msdcs .... que está no ForestDNSZone com as duplicatas que não estão em uso.
3 perguntas. Eu entendo as vantagens de ter DNS no ForestDNSZone.
então ...
-
Por que o DNS está usando o DomainDNSZone e isso é aceitável, considerando que o _msdcs ... está no ForestDNSZone?
-
Se sim, devo excluir o DC = 1.168.192.in-addr.arpa e DC = supernova.local do ForestDNSZone? Ou devo tentar fazer com que esses sejam os que estão em uso? Quais são esses passos? Eu entendo como excluir. Isso é simples, mas se eu precisar mover zonas, algumas informações serão avaliadas lá.
-
Apenas para confirmar. da minha compreensão. Eu posso deletar os dois duplicados no ForestDNSZone e deixar o _msdcs.supernova.local conforme necessário. Isso resolverá os erros que vejo.
Apenas fyi quando eu olho nessas pastas do ForestDNSZone eles têm apenas 2 e 1 entradas respectivamente. Então, obviamente, não está em uso em comparação com os outros. Tenho certeza de que entendi as etapas para concluir isso. Mas se você quiser fornecer essas informações, pontos de bônus!
Event Type: Warning
Event Source: DNS
Event Category: None
Event ID: 4515
Date: 1/4/2011
Time: 2:14:18 PM
User: N/A
Computer: STANLEY
Description:
The zone 1.168.192.in-addr.arpa was previously loaded from the directory partition DomainDnsZones.supernova.local but another copy of the zone has been found in directory partition ForestDnsZones.supernova.local. The DNS Server will ignore this new copy of the zone. Please resolve this conflict as soon as possible.
If an administrator has moved this zone from one directory partition to another this may be a harmless transient condition. In this case, no action is necessary. The deletion of the original copy of the zone should soon replicate to this server.
If there are two copies of this zone in two different directory partitions but this is not a transient caused by a zone move operation then one of these copies should be deleted as soon as possible to resolve this conflict.
To change the replication scope of an application directory partition containing DNS zones and for more details on storing DNS zones in the application directory partitions, please see Help and Support.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 89 25 00 00 %..
AND
Event Type: Warning
Event Source: DNS
Event Category: None
Event ID: 4515
Date: 1/4/2011
Time: 2:14:18 PM
User: N/A
Computer: STANLEY
Description:
The zone supernova.local was previously loaded from the directory partition DomainDnsZones.supernova.local but another copy of the zone has been found in directory partition ForestDnsZones.supernova.local. The DNS Server will ignore this new copy of the zone. Please resolve this conflict as soon as possible.
If an administrator has moved this zone from one directory partition to another this may be a harmless transient condition. In this case, no action is necessary. The deletion of the original copy of the zone should soon replicate to this server.
If there are two copies of this zone in two different directory partitions but this is not a transient caused by a zone move operation then one of these copies should be deleted as soon as possible to resolve this conflict.
To change the replication scope of an application directory partition containing DNS zones and for more details on storing DNS zones in the application directory partitions, please see Help and Support.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 89 25 00 00 %..
ATUALIZAÇÃO:
Sugestões para melhorar esta questão para que eu possa obter uma resposta seriam apreciadas.
UPDATE 2:
Nosso AD consiste em 3 CDs
Servidor em 192.168.1.100 é o nosso Exchange e um DC (infelizmente) É também o nosso servidor de arquivos. SO: Server 2003 R2
O servidor Stanley.DOMAIN.LOCAL é o nosso GC e mantém os shcemas, mas eu os moverei para o servidor DNS em breve. OS Server 2003 R2
O servidor DNS em 192.168.1.103 é o nosso novo 2008 R2 Box. Ele agora hospeda DNS e DHCP e também é um GC e vai ser o PDC assim que eu transferir esquemas.
Eu queria resolver esse problema de DNS primeiro.
Em uma tentativa, removi o DNS de todos os outros servidores e ele está sendo executado somente na nova caixa 2008 R2. Eu não vi nosso log DNS do Servidor 2008 R2 (Stanley) produzir o erro de evento desde o dia 11. Stanley costumava ser o DNS, mas agora está desligado. Poderia ser por isso que eu não vi o erro desde então?
Aqui está o diagrama de rede Ele foi executado no servidor do Exchange, pois ainda é o 2003 R2.
NETDIAG:
....................................
Computer Name: SERVERNAME
DNS Host Name: SERVERNAME.DOMAINNAME.local
System info : Microsoft Windows Server 2003 R2 (Build 3790)
Processor : x86 Family 6 Model 15 Stepping 6, GenuineIntel
List of installed hotfixes :
KB2079403
KB2115168
KB2160329
KB2183461-IE8
KB2229593
KB2286198
KB923561
KB924667-v2
KB925398_WMP64
KB925876
KB925902-v2
KB926122
KB926139-v2
KB927891
KB929123
KB930178
KB932168
KB933854
KB936357
KB938127
KB941569
KB942830
KB942831
KB943055
KB943460
KB943729
KB944338-v2
KB944653
KB945553
KB946026
KB948496
KB950760
KB950762
KB950974
KB951066
KB951748
KB952004
KB952069
KB952954
KB953298
KB954155
KB954550-v5
KB955069
KB955759
KB956572
KB956744
KB956802
KB956803
KB956844
KB958469
KB958644
KB958869
KB959426
KB960225
KB960803
KB960859
KB961063
KB961118
KB961501
KB967715
KB967723
KB968389
KB968816
KB969059
KB969883
KB969947
KB970238
KB970430
KB970483
KB971032
KB971468
KB971513
KB971657
KB971737
KB971961
KB971961-IE8
KB972270
KB973037
KB973354
KB973507
KB973540
KB973687
KB973815
KB973825
KB973869
KB973904
KB973917-v2
KB974112
KB974318
KB974392
KB974571
KB975025
KB975254
KB975467
KB975560
KB975562
KB975713
KB976323
KB976662-IE8
KB977165-v2
KB977290
KB977816
KB977914
KB978037
KB978251
KB978262
KB978338
KB978542
KB978601
KB978695
KB978706
KB979306
KB979309
KB979482
KB979559
KB979683
KB979907
KB980182
KB980182-IE8
KB980195
KB980218
KB980232
KB980302-IE8
KB980436
KB981332-IE8
KB982214
KB982381-IE8
KB982666
Q147222
Netcard queries test . . . . . . . : Passed
Per interface results:
Adapter : Local Area Connection 2
Netcard queries test . . . : Passed
Host Name. . . . . . . . . : SERVERNAME
IP Address . . . . . . . . : 192.168.1.100
Subnet Mask. . . . . . . . : 255.255.255.0
Default Gateway. . . . . . : 192.168.1.1
Dns Servers. . . . . . . . : 192.168.1.103
AutoConfiguration results. . . . . . : Passed
Default gateway test . . . : Passed
NetBT name test. . . . . . : Passed
WINS service test. . . . . : Skipped
There are no WINS servers configured for this interface.
Global results:
Domain membership test . . . . . . : Passed
NetBT transports test. . . . . . . : Passed
List of NetBt transports currently configured:
NetBT_Tcpip_{9052E7E6-EBB2-43F2-857A-8CF43C9718B3}
1 NetBt transport currently configured.
Autonet address test . . . . . . . : Passed
IP loopback ping test. . . . . . . : Passed
Default gateway test . . . . . . . : Passed
NetBT name test. . . . . . . . . . : Passed
Winsock test . . . . . . . . . . . : Passed
DNS test . . . . . . . . . . . . . : Passed
PASS - All the DNS entries for DC are registered on DNS server '192.168.1.103' and other DCs also have some of the names registered.
Redir and Browser test . . . . . . : Passed
List of NetBt transports currently bound to the Redir
NetBT_Tcpip_{9052E7E6-EBB2-43F2-857A-8CF43C9718B3}
The redir is bound to 1 NetBt transport.
List of NetBt transports currently bound to the browser
NetBT_Tcpip_{9052E7E6-EBB2-43F2-857A-8CF43C9718B3}
The browser is bound to 1 NetBt transport.
DC discovery test. . . . . . . . . : Passed
DC list test . . . . . . . . . . . : Passed
Trust relationship test. . . . . . : Passed
Secure channel for domain 'SUPERNOVA' is to '\stanley.DOMAINNAME.local'.
Kerberos test. . . . . . . . . . . : Passed
LDAP test. . . . . . . . . . . . . : Passed
Bindings test. . . . . . . . . . . : Passed
WAN configuration test . . . . . . : Skipped
No active remote access connections.
Modem diagnostics test . . . . . . : Passed
IP Security test . . . . . . . . . : Skipped
Note: run "netsh ipsec dynamic show /?" for more detailed information
The command completed successfullylution.
Eu também rodei um Diag DC no Weir. Esta é a caixa 2008 R2
Ele falhou neste teste. Embora Apenas olhasse para isso um pouco mais e percebesse se eu não fizesse adprep / rodcprep. Considerando que não estou planejando em um MS do RODC, pode ser ignorado.
Starting test: NCSecDesc
Error NT AUTHORITY\ENTERPRISE DOMAIN CONTROLLERS doesn't have
Replicating Directory Changes In Filtered Set
access rights for the naming context:
DC=ForestDnsZones,DC=DOMAINAME,DC=local
Error NT AUTHORITY\ENTERPRISE DOMAIN CONTROLLERS doesn't have
Replicating Directory Changes In Filtered Set
access rights for the naming context:
DC=DomainDnsZones,DC=DOMAINAME,DC=local
......................... WEIR failed test NCSecDesc