I have a working Exchange 2007 server in one of the Active Directory sites in my domain. I am attempting to install Exchange 2007 on a server with identical hardware at another AD site in the same domain; this server will serve as the target of SCR. Exchange reported the following warnings during installation. Warning: Setup cannot contact the primary DNS server (192.168.105.10) using TCP port 53. Check that the IP address of the DNS server is correct and that the DNS server is reachable. Warning: Setup cannot verify that the 'Host' (A) record for this computer exists within the DNS database on server 192.168.105.10. We used 192.168.x.x addresses at the source server's site before switching to 172.16.x.x addresses a few months ago. 192.168.105.10 was most likely the address of the domain controller at the site of the source. Machines at the target's site have 172.16.x.x addresses for years. Where is Exchange getting this old information, and how can I update it?

Hi, Exchange 2007 setup requires that the local computer have a valid HOST (A) record registered with the authoritative DNS database for the domain. Microsoft Exchange depends on DNS Host (A) records for the IP Address of its next internal or external destination server. To resolve this issue: Verify that the local TCP/IP configuration points to the correct DNS server. To verify the local TCP/IP configuration 1. Review the local TCP/IP configuration. For more information, see "Configure TCP/IP to use DNS" more info here: http://go.microsoft.com/fwlink/?LinkId=680942. Use Nslookup.exe to verify that the Host (A) record exists on the DNS server. more info here: http://go.microsoft.com/fwlink/?LinkId=63001 Regards from www.windowsadmin.info

Hi, Please try these steps. 1. In New Server, Goto Command prompt and Run nltest /dsgetsite. Make Sure its in New AD Site. If not Make sure the IP Address & DNS Configuration are suitable for New AD Site. You may move the Server to old site. Restart the Server. Move it back to New Site by changing the IP Configuration. Restart again. 2. Run nslookup command. Try to Resolve Your Primary Global catalog server NETBIOS, FQDN and 192.168.105.10 etc. If not Fix the DNS issues. 3. Make sure TCP Port 53 is not blocked by any Firewall. Open the port or Disable the Firewall. 4. If Possible Bring a Global Catalog in New site and Try again. 5. Make sure you have atleast one Exchange Transport role in New Site 6. Run Dcdiag /v /s:dcname > C:\dcdiag.txt. Check for any AD Issues. If yes, Fix them. 7. Run Netdiag /v > C:\netdiag.txt. Check for any NW Issue. If yes, Fix it. All the Best :) Sathish Kumar Elango MCSE 2003 & MCSA Messaging http://msexchangehelp.wordpress.com