Solved

Internal DNS settings for Exchange 2013

Posted on 2014-07-26
3
334 Views
Last Modified: 2014-07-27
I have setup an Exchange server and need help with my internal DNS configuration. The domain is example.local  The mail needs to be company.com for the email domain. (test@company.com for email)

In DNS under the Server there is forward lookup zones folder under example.com a "com" folder was created when I added CNAME, with name "mail" where the data is server.example.local  
When I double click on the record the FQDN is mail.company.com.example.local   The FQDN for target host is the server server.example.local   There is also an "owa" entry with the same data owa.comapny.com.example.local

Is this the correct place for DNS and the correct entry? The Exchange server is a stand alone server. Secondly does IIS need to be added to the server and configured in any way?
0
Comment
Question by:JRome225
  • 2
3 Comments
 
LVL 36

Accepted Solution

by:
Mahesh earned 500 total points
ID: 40221784
When you installed Exchange, its automatically installed IIS. No need to install it again

You have example.Local zone right?

Now you wanted mail.company.com and owa.company.com right?

Create new forward lookup zone in DNS named company.com and underneath create new records for owa and mail
do not create separate com folder
so the entries will look like below
mail.company.com
owa.company.com

I hope you have taken care external DNS name space already
0
 
LVL 1

Author Comment

by:JRome225
ID: 40222840
What about internal Autodiscovery, is a DNS record even necessary?
0
 
LVL 36

Expert Comment

by:Mahesh
ID: 40222872
For internal autodiscover function to work Service Connection Point (SCP) is already registered in active directory so internal clients can get autodiscovery automatically with AD
No need to setup special record for that
http://www.msexchange.org/articles-tutorials/exchange-server-2010/management-administration/exchange-autodiscover.html
0

Featured Post

PRTG Network Monitor: Intuitive Network Monitoring

Network Monitoring is essential to ensure that computer systems and network devices are running. Use PRTG to monitor LANs, servers, websites, applications and devices, bandwidth, virtual environments, remote systems, IoT, and many more. PRTG is easy to set up & use.

Question has a verified solution.

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

Issue: One Windows 2008 R2 64bit server on the network unable to connect to a buffalo Device (Linkstation) with firmware version 1.56. There are a total of four servers on the network this being one of them. Troubleshooting Steps: Connect via h…
Scam emails are a huge burden for many businesses. Spotting one is not always easy. Follow our tips to identify if an email you receive is a scam.
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…
The video tutorial explains the basics of the Exchange server Database Availability groups. The components of this video include: 1. Automatic Failover 2. Failover Clustering 3. Active Manager

773 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