как правильно настроить DNS для репликации AD между 2-мя DC внутри одного сайта?
 

ситуация такая: есть первичный и вторичный контроллеры домена. на каждом стоит днс сервер. зоны между ними пересылаются. репликация не работает из-за ошибки поиска в днс :(

режим работы 2003 сервер, в настройках подключения ip адреса dns серверов у самих себя выставлены (пробовал ставить друг на друга и сам на себя), нет файрволлов, инет через прокси, одна и та же подсеть.

есть ли простой гайд по основным моментам настройки днс? какие-то ключевые настройки без которых репликация работать не будет?

Номера ошибок в логах?
Пересылка зон и есть репликация. Уточните.

на обоих серверах dcdiag пишет следующее:

Testing server: Default-First-Site-Name\FILESERVER
Starting test: Connectivity
The host cf32f34d-f35e-4b5d-ac33-730242b15976._msdcs.sansan could not b
e resolved to an
IP address. Check the DNS server, DHCP, server name, etc
Although the Guid DNS name
(cf32f34d-f35e-4b5d-ac33-730242b15976._msdcs.sansan) couldn't be
resolved, the server name (fileserver.sansan) resolved to the IP
address (192.168.100.3) and was pingable. Check that the IP address
is registered correctly with the DNS server.
......................... FILESERVER failed test Connectivity

меняется только guid и ip-шник

у меня статические адреса и nslookup cf32f34d-f35e-4b5d-ac33-730242b15976._msdcs.sansan выдаёт правильный айпишник :(
где в зонах проверять наличие этого хоста? или создавать его?

в общем я создал два хоста вида {guid}._msdcs.domain с указанием айпишников и в обратной зоне.
теперь картина dcdiag поменялась:

Testing server: Default-First-Site-Name\FILESERVER
Starting test: Connectivity
*** Warning: could not confirm the identity of this server in
the directory versus the names returned by DNS servers.
If there are problems accessing this directory server then
you may need to check that this server is correctly registered
with DNS
......................... FILESERVER passed test Connectivity

Starting test: kccevent
An Warning Event occured. EventID: 0x80000785
Time Generated: 10/08/2007 17:15:26
Event String: The attempt to establish a replication link for
An Warning Event occured. EventID: 0x80000785
Time Generated: 10/08/2007 17:15:26
Event String: The attempt to establish a replication link for
An Warning Event occured. EventID: 0x80000785
Time Generated: 10/08/2007 17:15:26
Event String: The attempt to establish a replication link for
An Warning Event occured. EventID: 0x80000785
Time Generated: 10/08/2007 17:16:49
Event String: The attempt to establish a replication link for
An Warning Event occured. EventID: 0x80000785
Time Generated: 10/08/2007 17:16:49
Event String: The attempt to establish a replication link for
An Warning Event occured. EventID: 0x80000785
Time Generated: 10/08/2007 17:16:49
Event String: The attempt to establish a replication link for
......................... FILESERVER failed test kccevent
Starting test: systemlog
An Error Event occured. EventID: 0x40000004
Time Generated: 10/08/2007 17:11:54
Event String: The kerberos client received a
......................... FILESERVER failed test systemlog
-------------------------------------------------------------------------------------------------------------------

Testing server: Default-First-Site-Name\SERVER
Starting test: Connectivity
*** Warning: could not confirm the identity of this server in
the directory versus the names returned by DNS servers.
If there are problems accessing this directory server then
you may need to check that this server is correctly registered
with DNS
......................... SERVER passed test Connectivity
Doing primary tests

Testing server: Default-First-Site-Name\SERVER
Starting test: Replications
[FILESERVER] DsBindWithSpnEx() failed with error 1722,
Сервер RPC недоступен..
Starting test: KnowsOfRoleHolders
Warning: FILESERVER is the Schema Owner, but is not responding to DS RP
C Bind.
[FILESERVER] LDAP search failed with error 58,
Указанный сервер не может выполнить требуемую операцию..
Warning: FILESERVER is the Schema Owner, but is not responding to LDAP
Bind.
Warning: FILESERVER is the Domain Owner, but is not responding to DS RP
C Bind.
Warning: FILESERVER is the Domain Owner, but is not responding to LDAP
Bind.
Warning: FILESERVER is the PDC Owner, but is not responding to DS RPC B
ind.
Warning: FILESERVER is the PDC Owner, but is not responding to LDAP Bin
d.
Warning: FILESERVER is the Rid Owner, but is not responding to DS RPC B
ind.
Warning: FILESERVER is the Rid Owner, but is not responding to LDAP Bin
d.
Warning: FILESERVER is the Infrastructure Update Owner, but is not resp
onding to DS RPC Bind.
Warning: FILESERVER is the Infrastructure Update Owner, but is not resp
onding to LDAP Bind.
......................... SERVER failed test KnowsOfRoleHolders
Starting test: RidManager
......................... SERVER failed test RidManager
Starting test: frsevent
There are warning or error events within the last 24 hours after the
SYSVOL has been shared. Failing SYSVOL replication problems may cause
Group Policy problems.
......................... SERVER failed test frsevent
------------------------------------------------------------------------------------------------------------------------
всё что passed test я не привожу.

Имя домена из одной метки, что ли? Тогда http://support.microsoft.com/kb/300684/ru