Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

I am in a real bad bind. We are currently moving to a hosted virtual private server for our website, and Google Apps Premier for email from an on-site MS Exchange 2003 server handling both functions.

The problem is that we have redirected the DNS for the domain to the new server, which has broke our exchange email. I had an AName in place for the URL that we use to access our mail (i.e. mail.ourdomain.com - points back to the exchange server IP) - however it's starting to look like that's not going to cut it.

How can I configure my email traffic to flow through our new server toward the old exchange server using DNS settings?

Update: So now I have:

    mail.DOMAIN.COM.    (A record)  10.10.10.10 (IP Address of Exchange server.) 
AND   DOMAIN.COM              (MX record)    mail.DOMAIN.com

I don't have a CNAME involved, but this should still route mail through the new server to our onsite Exchange server, correct? As of now, I can log into exchange with https://10.10.10.10/exchange and send mail, but incoming mail is still bouncing. I just want to be sure I'm not having an issue with ports or anything else...

share|improve this question
    
Your question is essentially the same as this one: serverfault.com/questions/98625/… (and dozens of others on SF already) - except replace the MX details with your Exchange details –  Mark Henderson Jan 10 '10 at 20:49
    
I would say that question is similar but not the same. I wasn't sure if there were other considerations in transferring mail to MS Exchange 2003 - not Google Apps (yet) –  cinqoTimo Jan 10 '10 at 21:51
add comment

1 Answer

up vote 0 down vote accepted

You use the MX records to "tell the internet" where to send your mail.

  1. have A record for mail.domain.com
  2. insert MX records pointing at mail.domain.com

In BIND syntax the scenario might look like:

mail  IN  A  1.2.3.4
       IN  MX  10  mail.domain.com.

Clarify your problem more if this doesn't fix it.

share|improve this answer
    
Thanks. I had the ANAME, but my MX record was wrong. It's still kicking back mail, but I assume that it updates like other DNS setting changes. –  cinqoTimo Jan 10 '10 at 21:05
    
FYI, it's just called an "A" record -- there's something called a CNAME that is also DNS, but not an "ANAME" - just so you don't confuse people. :) DNS has a serial number in it -- so, after fixing your MX then make sure the serial is incremented (typical BIND serial numbers are YYYYMMDDXX where XX is 01, 02, 03, etc.) and be sure to push the zone upwards (again, with BIND using the rndc tool, 'rdnc reload zone_file'). Due to your TTL already sent to the world it'll probably take 24hrs to get to a lot of places, 48hrs to be safe. –  troyengel Jan 11 '10 at 3:52
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.