Internal DNS settings for Exchange 2013

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?
LVL 1
JRome225Asked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

MaheshArchitectCommented:
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

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
JRome225Author Commented:
What about internal Autodiscovery, is a DNS record even necessary?
0
MaheshArchitectCommented:
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
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Exchange

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.