civir
asked on
Redundant ISP for Email Server
I have one Exchange 2010 Server 2008R2 on a local domain (domain.local) with two ISP.
Isp 1 has the DNS and PTR set already as mail.domain.com. I would like to setup my second static ip to have the same settings as my first, so that if the first goes down my service remains live (don't know if this can create a conflict)
Questions:
1. How do I configure the second IP record? would it be mail1.domai
if so can't I use the same mail.domain.com to resolve both IP's rather than mail.domain.com AND mail1.domain.com?
2. Does the mail.domain.com AND mail1.domain.com make a difference with any configurations I may have to do on my Exchange 2010 servers?
Please advise urgently.
Isp 1 has the DNS and PTR set already as mail.domain.com. I would like to setup my second static ip to have the same settings as my first, so that if the first goes down my service remains live (don't know if this can create a conflict)
Questions:
1. How do I configure the second IP record? would it be mail1.domai
n.com to the static IP?if so can't I use the same mail.domain.com to resolve both IP's rather than mail.domain.com AND mail1.domain.com?
2. Does the mail.domain.com AND mail1.domain.com make a difference with any configurations I may have to do on my Exchange 2010 servers?
Please advise urgently.
ASKER
What do I put in the FQDN? would I put the mail1.domain.com and used the same mail1.domain.com with my redundant IP for DNS/PTR creation?
Yes, I believe so.
ASKER
With my redundant IP and exchange: if I set my second ip to mail1.domain.com will this affect my current OWA that is mapped to mail.domain.com and if so How can I ensure my OWA is up when I switch to my secondary IP when my mail.domain.com linked to my OWA goes down.
While using OWA, you'd have to use mail1.domain.com/OWA as you would be coming in another way.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
2. In DNS, update your current TXT record for the SPF validation. http://www.microsoft.com/mscorp/safety/content/technologies/senderid/wizard/
You probably know this, but make sure port 25 isn't being blocked as well.