Point @domain.org to exchange server, not webhost.
I'm new to setting up an exchange server. I have Server 2008 Standard SP2 with Exchange 2010 on it. The problem I'm having is setting up exchange 2010 on it. I have exchange installed. Right now our webhost (powweb.com) handles the emails and we map to pop.powweb.com or smtp.powweb.com. They also handle our website (We'll call it domain.org). How can I point the emails @domain.org to our exchange server so they can handle them but keep our webhosting on powweb?
I have the dns records on my dns server of:
(same as parent folder) MX 10 mail.domain.org
* Alias (CNAME) domain.org
www Host (A) <IP OF DOMAIN.ORG>
The internal routing of exchange is working (Sending emails between users with a @domain.org address). Its just outgoing and receiving. The incoming emails are still going to powweb.
My next question is, what about firewall ports. Which ones should I have open so Exchange ActiveSync works along with OWA, and incoming / outgoing emails?
I have the dns records on my dns server of:
(same as parent folder) MX 10 mail.domain.org
* Alias (CNAME) domain.org
www Host (A) <IP OF DOMAIN.ORG>
The internal routing of exchange is working (Sending emails between users with a @domain.org address). Its just outgoing and receiving. The incoming emails are still going to powweb.
My next question is, what about firewall ports. Which ones should I have open so Exchange ActiveSync works along with OWA, and incoming / outgoing emails?
ASKER
So my MX Record should be the public IP provided by our ISP? Also, I see you have owa.domain.org. If I want mail.domain.org to point to our OWA, can I just change owa.domain.org to mail.domain.org? The only other problem is powweb has mail.domain.org pointing to their webmail hosting already (mail.powweb.com).
ASKER
My domain name (domain.org) is through Network Solutions. Is there anything I have to adjust on the DNS for that? I'm assuming I have to do:
An MX record, pointing to public IP of Exchange 2010.
An A record, www.domain.org pointing to powweb web server IP
An A record, owa.domain.org pointing to the public IP of Exchange 2010
to the network solutions domain.org dns in addition to my dns server?
An MX record, pointing to public IP of Exchange 2010.
An A record, www.domain.org pointing to powweb web server IP
An A record, owa.domain.org pointing to the public IP of Exchange 2010
to the network solutions domain.org dns in addition to my dns server?
ASKER CERTIFIED SOLUTION
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.
ASKER
On Network Solutions MX records, it says Current Domain: domain.org. Then it has a spot to add a new 'domain', not an IP. How would I go about this? I tried to enter my IP but it keeps saying its invalid and shows an ex. mail-domain.com
Ok, not used Network Solutions before! Modify the A record for mail.domain.org to point to your Exchange server's public IP first, then use mail.domain.org for the MX record.
Sam
Sam
ASKER
Okay, I'm going to give that a shot and hopefully that works. I will let you know once Network Solutions updates the DNS.
ASKER
Do I have to do anything with the SMTP or is that covered under the MX record?
ASKER
I just tried to send my self a test email seeing that Network Solutions is updated. The test email didn't come through on my powweb pop3 nor the exchange server. I have it pointing to the IP now. Is there something I have to setup to receive the emails? I thought I setup the Hub Transport correctly...
Make sure you have "anonymous" allowed on the default receive connector on the Hub Transport server.
Sam
Sam
ASKER
Yeah thats done. I just tried the https://www.testexchangeconnectivity.com Its saying port 25 isn't open. I'm looking at the pfSense firewall settings now and its showing its open. Hmmmm. Its showing port 25 is open the network 10.1.10.0/24. I'll change it to the direct ip of the exchange server, 10.1.10.50 and see if that fixes it.
That's the problem then - you need to make sure the public IP is mapped to the private IP of the Exchange server (10.1.10.50) and port 25 is open on your firewall.
Sam
Sam
ASKER
It keeps saying:
Testing TCP port 25 on host mail.delranems.org to ensure it's listening and open.
The specified port is either blocked, not listening, or not producing the expected response.
For my firewall, I have:
LAN:
TCP/UDP 10.1.10.50/24 * * 25 (SMTP) *
WAN is:
TCP/UDP * 25 (SMTP) 10.1.10.50 * * Allo
Testing TCP port 25 on host mail.delranems.org to ensure it's listening and open.
The specified port is either blocked, not listening, or not producing the expected response.
For my firewall, I have:
LAN:
TCP/UDP 10.1.10.50/24 * * 25 (SMTP) *
WAN is:
TCP/UDP * 25 (SMTP) 10.1.10.50 * * Allo
ASKER
I just thought about something... Comcast blocks port 25 on modems by default I believe.... Is there anyway to use port 465 instead?
ASKER
Okay, I finally got it to work. Now, how do I view the default pop settings?
If you create an MX record to point to the public IP address of your exchange server it will not affect your A record for www.domain.org. If you plan to use owa/activesync then you can point another A record at the same IP.
So, your dns setup will be:
An MX record, pointing to public IP of Exchange 2010.
An A record, www.domain.org pointing to powweb web server IP
An A record, owa.domain.org pointing to the public IP of Exchange 2010
Incoming, you will need SMTP (port 25) for mail, HTTPS (port 443) for OWA and ActiveSync. Using HTTP (port 80) is not a recommended setup, but you might want to open that port and redirect it to HTTPS.
Sam