How to configure mx records so that I can receive and send emails from my new exchange server

I just set up Exchange Server 2010. I also have a 2008 server running my DC.

I have configured everything that I believe is needed on the exchange end. Where I am confused is on the MX side.

I got my MX records from hostgator (host my email). They gave me A records and cname records with an Ip address. I have a host record created on the server which of course is done automatically.

I created a MX record and put in my FQDN and server priority of 0. I am not sure if i need to be using the ip address giving by my email host provider and if so where do i enter that info. Do i create a host record with that ip and create a mx record to point to that host record?

Can someone please help out. I need this up and running asap. I will be standing by waiting for some help. I am new to exchange so please be specific when replying thanks.

Your MX record needs to be the incoming mail servers that hostgator provided to you. Don't use the IP, but rather use the hostname that they provided to you.

If the MX record(s) they provided you have a domain of your own (ie: mail.yourdomain.com), then yes you will need to create A record(s) for any of those hostnames, then point your MX record(s) to those hostnames.

you have the domain of testdomain.com -- you would create the following records (on external DNS server) or with DNS host:

1) A record similar to the following: mail pointing to external Ip of exchange
2) MX record for mail.testdomain.com - pointed to external IP of exchange (lowest priority wins) default is 10
3) PTR record for MX (using configured by ISP = external IP resolves to FQDN of MX record

Veeam® is happy to provide the Microsoft community with a study guide prepared by MVP and MCT, Orin Thomas. This guide will take you through each of the exam objectives, helping you to prepare for and pass the examination.

ok so i have a A record that says example-dc (with the ip address of the dc, which is also the exchange server)
and a mx record that under host or child domain: i put mail.example.com (that's the info i got from the mail host provider) and the FQDN i just browsed to the DC. Server priority is set to 10.

IS there anything else that is missing? I sent several messages and they are still stuck in the queue, do i have to wait the 24-48hrs? or am i missing something else?

when did you change SPs? It sounds in part like you are having DNS resolution issues . This is common with ISP and DNS changes because of changes to DNS servers , Records, etc because of the existing TTL (time to live) of your current records (typically 48 + hrs) by default.

Have your DNS nameservers changed? what is the current TTL of your records?

I created this exchange server and DC this morning. The TTL is set to 4hrs according to toolbox. DNS servers have not changed again because this is a new DC\Exchange server that i configured this morning.

these are the results from the smtp test

220-gator1595.hostgator.com ESMTP Exim 4.69 #1 Sun, 30 Oct 2011 22:45:47 -0500 We do not authorize the use of this system to transport unsolicited, and/or bulk e-mail.
OK - 216.172.179.126 resolves to 7e.a0.acd8.static.websitewelcome.com
Warning - Reverse DNS does not match SMTP Banner
0 seconds - Good on Connection time
Not an open relay.
0.140 seconds - Good on Transaction time

Session Transcript:
HELO please-read-policy.mxtoolbox.com
250 gator1595.hostgator.com Hello please-read-policy.mxtoolbox.com [64.20.227.133] [0 ms]
MAIL FROM: <supertool@mxtoolbox.com>
250 OK [31 ms]
RCPT TO: <test@example.com>
550-(please-read-policy.mxtoolbox.com) [64.20.227.133]:56995 is currently notpermitted to relay through this server. Perhaps you have not logged intothe pop/imap server in the last 30 minutes or do not have SMTPAuthentication turned on in your email client. [62 ms]
QUIT
550-(please-read-policy.mxtoolbox.com) [64.20.227.133]:56995 is currently notpermitted to relay through this server. Perhaps you have not logged intothe pop/imap server in the last 30 minutes or do not have SMTPAuthentication turned on in your email client. [16 ms]

Who is old? Who is new? I am not trying to be redundant -- just want to make sure we are clear here.. who do you want to be pointing at ? are you using a smarthost type setup? or are you your own host?

no.. if hostgator is your host, you just need to make sure they have the proper records, if they are providing records, you will use the FQDN of the records they give you and make sure the proper IPs are pointing to those records. what do you get for the following records if you run an nslookup against your domain?

A = record for fqdn of mail server (ex. mail.domain.com)
MX = domain.com

are the IPs correct on the lookup ? If not, they would need to be changed to the correct one with the DNS host

ok, just to be clear we should have multiple records, even though it seems redundant... for example: if I own domain community.org and I want to send / receive mail here is what I need: We will assume I host DNS through a provider
my external IP for exchange is 1.2.3.4
I determine that the FQDN of my mail server is going to be mail.community.org (what the server is going to respond as when another mail server attempts to connect to it) you should also have the fqdn of the server as your SMTP banner on your exchange server (but we wont worry about that yet) --

Exchange server FQDN is set for mail.community.org
Exchange has authority for community.org domain and has recipient policy for it.
Receive connector allows mail from everyone
Send connector allows exchange server to send to all domains

THe receive connector is set up with two connectors. Client example.com and default example.com
under network i have all available ipv6 and ipv4 port 587 and receive mail from remote server with open ip address. 0.0.0.0 255.255.255.255

Under accepted domains i have my internal domain there.

Under send connectors -> address space tab i have an * for address with a cost of 1 fot type= smtp

I have it set to use dns "mx" records to route mail automatically.

I created another host record with the ip 216.172.179.126 that was provide by hostgator. THen I created a mx record to point to that host record with the external ip address 216.172.179.126. and the fqdn is example.com.example.local (example.com is what i got from hostgator that was associated with the ip address.

under com zones i have two records. A MX record that says mail.example.com.example.local with a priority of 10. and a host A record with example.com.example.local and the FQDN and an ip of 216.172.179.126.

Sounds mostly like default connectors -- you will want one that is something like INBOUND from INTERNET and set it up for the internal IP of your server -- on port 25 from 0.0.0.0 - 255.255.255.255 and under the perm groups tab - anonymous and the fqdn would be the same as your mx record.

Under Use these local ip addresses to receive mail:
all available ipv6 and ipv4 and I added my internal ip address which is 10.10.10.90 on port 25.
Under receive mail from remote server that have these ip addresses i have :
start address: 0.0.0.0 and end address: 255.255.255.255

These settings are under default connectors

Under permission groups I have Exchange users, exchange servers, and Legacy exchang eservers checked off. Anonymous and Partners are not checked.

Ok, lets go back to beginning here for a second..lets just confirm a few things...

1) your router is set to allow 25,443 from anyone from the outside and NAT port 25,443 down to your exchange server(also 80 if you are going to use a OWA redirect of any kind)

2) You have an accepted domain configured -- Under Organization Config -- hub transport -- you will need to define your external domain name here to allow the server to have authority to receive mail for your domain

- Can you send receive mail internally ok? Just outside having trouble?

3) Also under OC - HT - you will want email address policies configured - as well as Send Connector (Something like OUTBOUND TO INTERNET) - specify the fqdn of your mx record for HELO EHLO - Address Space should be type SMTP - Address (*) - Cost 1 -- Network - Use MX to route - Source Server should reflect the hostname of your Exhcnage Server and show the roles configured

4) Your Server Config - Hub Transport
Client <servername>
Default <servername> should both be enabled and should not need to be modified - they were created by default

Create a Receive Connector Called INBOUND FROM INTERNET or something you can remember -- General - use fqdn of MX record for EHLO HELO
Network
Change "use these local IP addresses.." to show the actual IPv4 address of your server on port 25
Receive mail from remote servers that ...
0.0.0.0 - 255.255.255.255
Authentication
TLS
Permission Groups
Anonymous -- needs to be done for external receive connector (from outside)
Your two other defaults mentioned earlier take care of internal routing of email. This is for you to receive mail from outside world.

Once we have these steps confirmed we can test - use Exchange Connectivity Tester or MXtoolbox to test - We can then make sure DNS Records and entries are correct..

With so many activities to perform, Exchange administrators are always busy in organizations. If everything, including Exchange Servers, Outlook clients, and Office 365 accounts work without any issues, they can sit and relax. But unfortunately, it…

In this Micro Video tutorial you will learn the basics about Database Availability Groups and How to configure one using a live Exchange Server Environment.
The video tutorial explains the basics of the Exchange server Database Availability grou…

There are cases when e.g. an IT administrator wants to have full access and view into selected mailboxes on Exchange server, directly from his own email account in Outlook or Outlook Web Access. This proves useful when for example administrator want…