AD & DNS synchronization

Hi,
Have you changed the Ip address of either server since they were built? Basically, each server PULLS rather than PUSHES updates from it's replication partners. in the case of integrated DNS, server A will look in ITS OWN dns database for serverB's SRV record (IE the service record that identifies B as a dc). Now, if server B has it's address changed, when server A tries to pull from it (and looks in it's own database) it will find the old IP, and try to use that. As the old IP is no longer used by server B, replication fails. Moreover, server A will NEVER find out about server B's new address, because it will never be able to successfuly sync. This known 'feature' is commonly called 'the island problem'. the quickest fix is to set the primary DNS address on server A to server B, and vice versa. Now an ipconfig /registerdns will cause each server to register DIRECTLY with it's opposite number, updating it with the correct address. afterwards, set each servers primary DNS back toitself. Hope I'm on the right track here......