Celebrate National IT Professionals Day with 3 months of free Premium Membership. Use Code ITDAY17


DNS Configuration for Exchange Server 2010

Posted on 2015-01-31
Medium Priority
Last Modified: 2015-02-15
Good afternoon experts,

I am installing my first Exchanger Server and I need some clarification. It's probably really simple but I'm having a hard time finding a straight forward explanation:

Please find below a setup to better understand my issue:

I have a server (SERVER1 IP: that is the Domain Controller and DNS for the network.
I have a second server (SERVER2 IP: where I installed Exchange Server 2010.
My External IP in
My domain name is: domainname.com

The DNS Entries are as follows:
domainname.com    Start of Authority     server1.domainname.com, hostmaster.domainname.com
domainname.com    Name Server (NS)     server1.domainname.com   IP:
domainname.com    Name Server (NS)     server2.domainname.com   IP:

The nameserver to contact the server is "mail" so:
domainname.com    Name Server (NS)     mail.domainname.com.    IP:

Mail Exchanger Entry
domainname.com     Mail Exchanger (MX)        [10] exchange.domainname.com

Then my A Host:
domainname.com    Host (A)
domainname.com    Host (A)
server1                       Host (A)
server2                       Host (A)
mail                             Host (A)
exchange                   Host (A)
www                           Alias (CNAME)       domainname.com.

To test it, I used Outlook web Access to see if I can connect.
I'm know I'm missing something as, internally and externally I cannot use https://exchange.domainname.com/owa however internally I can use https://server1.domainname.com/owa and it works.

The router is not the issue as all the ports are open and the MX records have also been modified for the Domain Name's DNS entries.

Using NSLOOKUP, here are my results:
for domainname.com
Name: domainname.com

then set type =mx
domainname.com MX preferences = 10, mail exchanger = exchange.domainname.com
exchnage.domainname.com      internet address =

lastly, set type=ns
Server: localhost

domainname.com nameserver = server2.domainname.com
domainname.com nameserver = server1.domainname.com
server2.domainname.com      internet address =
server1.domainname.com      internet address =
mail.domainname.com            internet address =

I'm not sure what's wrong but I suspect that I'm missing a step in the DNS that connects the mail.domainname.com or exchange.domainname.com to the actual server (SERVER2) whis is the Exchange Server.

I really hope someone can help me out.

Cheers and thank for taking the time :)
Question by:TSIsolutions
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
LVL 20

Assisted Solution

by:Satya Pathak
Satya Pathak earned 400 total points
ID: 40581922
follow the below KB woudl help you to understand how to configure a DNS  with Exchange enviroment
LVL 79

Accepted Solution

arnold earned 800 total points
ID: 40581978
The issue is not with DNS, the issue is that you need to create a rule on your firewall allowing connection attempts on your public IP port 25 to get to your exchange server port 25.

Dealing with access to OWA it is he same, you need to create a path on port 443 of your existing external IP to the internal. The second thing you need to add to the IIS configuration for OWA to also treat requests for exchange.domainname.com, but since you use secure, you may need a certificate using a SAN exchange.domainname.com and mail.domainname.com

Double check what people outside your domain will see as a response.  Run the Sam nslookup queries but use an external DNS server
nslookup -q=mx domainname.com.

Since you've not included a domain name, we have to rely on your description to assess what is wrong and what needs fixing.  Your issue could be all together something else I.e. A restriction on the incoming connector to only allow requests from network, ......
LVL 11

Assisted Solution

hecgomrec earned 800 total points
ID: 40583954
Since Exchange 2007 it is recommended to use the same names for your exchange server internally and external access.

For exchange to be accessed from outside your organization you will have to have an MX record and a DNS name created for your server name: mail.domainname.com.  Then you will have to create a rule on your firewall to either pass all request or just some ports (25, 80, 443, etc.) to mail.domainname.com IP to your internal exchange server's IP (

Second step will be to go to your DC/DNS server ( and create an MX record and a Host record for mail.yourdomainname.com  --->

Last step, make sure your server internal and external names match,  Open the EMC, Under Server Configuration, Client Access, locate in the middle of the screen: Outlook Web App tab open the properties and check that internal and external URL in the General tab match (mail.yourdomainname.com), repeat the process for the others tabs to match your domain name and the virtual path needed.

This should take care of the access problem, Now if you still have problems check if you have installed a valid certificate to handle all your services.  Click on Server configuration, in the middle on the screen locate available installed certificates under "Exchange Certificates" tab.  Here, if you don't have a valid certificate you must get one and install it following your CERT Authority provider, remember the certificate should include all possible names the server will have (mail.domainame.com, owa.domainame.com, webmail.domainame.com, etc.).

Hope that helps!!!

Author Closing Comment

ID: 40611493
Good afternoon,

Sorry for the late reply and thanks for the comments. In my case it turns out that the firewall on the router for port 25 was poiting to a different IP address.
Additionally, the previous IT company had installed SMTP service on the the server while we created a connector on port 25. Because of that the binding to the connector was failing because the port was already in use.
I feel a bit stupid as I had seen the port opened on the firewall rules but did not notice the IP address it was pointing to another IP address.
As soon as I changed it, and removed the SMTP service, everything was fine.

Thanks again guys :)

Featured Post

Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

If you troubleshoot Outlook for clients, you may want to know a bit more about the OST file before doing your next job. IMAP can cause a lot of drama if removed in the accounts without backing up.
Know the reasons and solutions to move/import EDB to New Exchange Server. Also, find out how to recover an Exchange .edb file and to restore the file back.
The basic steps you have just learned will be implemented in this video. The basic steps are shown to configure an Exchange DAG in a live working Exchange Server Environment and manage the same (Exchange Server 2010 Software is used in a Windows Ser…
This Micro Tutorial hows how you can integrate  Mac OSX to a Windows Active Directory Domain. Apple has made it easy to allow users to bind their macs to a windows domain with relative ease. The following video show how to bind OSX Mavericks to …
Suggested Courses

730 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question