Gary:

It sounds good.

I think your replication must be working now.

Know in the clients from your remote site configure the DNS Client to point
to the local DNS as primary DNS address, and the Central Site DNS as the
secondary DNS address.

Regards.

Oscar Soto Casali
MVP Directory Services
"gstar" <gary.brett@gmail.com> escribió en el mensaje de
noticias:1161891491.168353.8050@m7g2000cwm.googleg roups.com...
> Hi Oscar,
>
>> I saw the diagram and you have to change the IP address of Secondary DC
>> Domain1 (192.168.45.11) to an ip of the 192.168.254.0 range.
>
> I have done that, changed the DNS & WINs properties, and IPCONFIG now
> looks like this on Secondary DC:
>
> Physical Address. . . . . . . . . : 00-0B-DB-D5-14-
> DHCP Enabled. . . . . . . . . . . : No
> IP Address. . . . . . . . . . . . : 192.168.254.21
> Subnet Mask . . . . . . . . . . . : 255.255.255.0
> Default Gateway . . . . . . . . . : 192.168.254.1
> DNS Servers . . . . . . . . . . . : 192.168.45.10
> 192.168.254.2
> Primary WINS Server . . . . . . . : 192.168.45.10
> Secondary WINS Server . . . . . . : 192.168.254.2
>
> If I make changes to the original DC [AD or DNS] they replicate
> instantly over to the secondary so that appears to be working.
>
>> Try to configure this server as a DNS and replicate the Active Directory
>> DNS Zone to all DC over the forest.
>
> The secondary DNS already replicates from DC, is that what you meant?
>
> Thanx again
> Gary
>