So heres a quick summary of whats happening. I have inherited a huge DNS mess. We have external entries hosted through GoDaddy.com and two internal DNS servers. I also have just installed a second exchange server, and I am in the process of removing the first server. Before I remove any servers, I want to ensure that the e-mail continues to route correctly. I have followed all steps outlined in http://support.microsoft.com/kb/822931
Currently in the GoDaddy control panel, I have an @ record that points to the public url of my webserver (126.96.36.199). I have an MX record that lists mail.luceresearch.com with a priority of 10 that points to the host @. If I check this on www.mxtoolbox.com
it resolves correctly to the IP address 188.8.131.52.
The new mail server is located at the public IP address 184.108.40.206. How would I configure this in GoDaddy's DNS control to point my MX record at my new server IP?
Next - Internal DNS....
Oy - its a bigger mess. I have the forward lookup zone lucer.luceresearch.local, luceresearch.com, and luceresearch.org. All names and private IP's are listed in the .local zone. In the luceresearch.com forward lookup, there are A records that point to the private IP (i.e. www points to 192.168.0.6) for DNS resolution within the intranet. In the luceresearch.org I have two A records: mail that points to private IP (192.168.0.6) and mail: that points to public IP (220.127.116.11). The MX record is listed in this zone as mail, MX, and points to mail.luceresearch.org.
I want to make sure that I can point the MX record to the new exchange server before I remove the first one from the site. I appreciate any advice.