At work I recently migrated exchange from 2000 to 2007 and everything is working however we are also changing ISP so we will be getting a new IP address. Now currently we have our MX records setup like:
0 new-servername.domain.com
1 mail.domain.com
2 old-servername.domain.com
reason we still have old-server.domain.com is because the reverse DNS points here.
Now i am just wondering do we need more than 1 mx record for a single domain enterprise?
Could i get away with just having mail.domain.com? I would like to get this sorted so we can tell our ISP the correct reverse DNS...
Also how do A records work e.g. we currently have an ftp.domain.com which points to our IP address which when it comes in gets filtered through the firewall on the relevent port to the ftp server. Now we would like to use exchange OWA and activesync and currently use https://new-server.domain.com/site however is this correct? Should we just use mail.domain.com or have an A record which goes to owa.domain.com????
Any help appreicated. And sorry if these appear to be silly stupid questions
0 new-servername.domain.com
1 mail.domain.com
2 old-servername.domain.com
reason we still have old-server.domain.com is because the reverse DNS points here.
Now i am just wondering do we need more than 1 mx record for a single domain enterprise?
Could i get away with just having mail.domain.com? I would like to get this sorted so we can tell our ISP the correct reverse DNS...
Also how do A records work e.g. we currently have an ftp.domain.com which points to our IP address which when it comes in gets filtered through the firewall on the relevent port to the ftp server. Now we would like to use exchange OWA and activesync and currently use https://new-server.domain.com/site however is this correct? Should we just use mail.domain.com or have an A record which goes to owa.domain.com????
Any help appreicated. And sorry if these appear to be silly stupid questions