Solved

Configuring public DNS for Exchange records

Posted on 2011-09-21
16
245 Views
Last Modified: 2012-05-12
I would like to understand the DNS records that are configured at the registrar, for instance Godaddy.com

(A) Host record
SMTP----------------->62.62.63.64
CNAME
Owamail------------->SMTP.mycompany.com

MX record
@---------> smtp.mycompany.com

so if the DNS settings above are correct, what do users type on the browse?


thanks
0
Comment
Question by:jskfan
  • 8
  • 5
  • 3
16 Comments
 
LVL 21

Expert Comment

by:Papertrip
Comment Utility
They type whatever the address is of OWA, so in this case https://smtp.mycompany.com
0
 

Author Comment

by:jskfan
Comment Utility
so the CNAME is not helpful in this case?
0
 

Author Comment

by:jskfan
Comment Utility
I wanted to be Owamail.mycompany.com
0
 
LVL 70

Expert Comment

by:Chris Dent
Comment Utility
That's the target of the CNAME, I guess jskfan wants the more friendly name, making it:

https://owamail.mycompany.com

But both should work.

Chris
0
 

Author Comment

by:jskfan
Comment Utility
I want the logic based on the DNS records posted above.
because if a user types https://owamail.mycompany.com the namespace is pointing to an A record smtp.mycompany.com which points to the IP address of the external interface of the router   62.62.63.64.
I don't see the logic that goes through the MX record.
you see my point?
0
 
LVL 21

Assisted Solution

by:Papertrip
Papertrip earned 166 total points
Comment Utility
MX record plays no part in how your users access OWA.  MX records tell mail servers where to send mail for a specific domain.
0
 

Author Comment

by:jskfan
Comment Utility
do you mean  from exchange to outside on the internet not the other way around?
0
 
LVL 70

Accepted Solution

by:
Chris Dent earned 334 total points
Comment Utility
From outside in, so the MX is used by people sending mail to your domain. It's not used for anything else.

Chris
0
Want to promote your upcoming event?

Are you going to an event? Are you going to be exhibiting at a tradeshow? Talking at a conference? Using a promotional banner in your email signature ensures that your organization’s most important contacts stay in the know and can potentially spread the word about the event.

 

Author Comment

by:jskfan
Comment Utility
That's what I understood...
But considering the Records I posted (if they are coorect), how does the MX record come into play.
You would think when  a user enters :
owamail.mycompany (CNAME), it will point straight to (A) record smtp.mycompany.com which sends them to 62.62.63.64

it looks like even if MX record was not there, it will still work.

***can you please give me the route taken by the requests to DNS ? for instance...

Client--->CNAME---A record--IP ---MX---IP -->etc.... until it gets the externa interface of the company firewall ???

thanks
0
 
LVL 21

Expert Comment

by:Papertrip
Comment Utility
As I said in my previous post, MX record does not come into play in regards to your users accessing OWA.  It is only for other mail servers to send mail to your domain.

client -> cname -> a record -> owa
0
 
LVL 70

Expert Comment

by:Chris Dent
Comment Utility
Papertrip is absolutely right, the MX is not relevant for people using OWA, OWA would work perfectly well if the MX wasn't there.

Of course, inbound mail for your domain might go a bit wrong without it, so I doubt anyone will advise you remove it :)

Chris
0
 

Author Comment

by:jskfan
Comment Utility

OWA can work on port 80 (not secure) or 443(SSL- secure)
let s say we have another web application that can use the same ports.

without the MX record on the internet DNS, how would it know if it needs to forward the connection request to an Exchange server, or to another web server ???

0
 
LVL 70

Expert Comment

by:Chris Dent
Comment Utility
MX has nothing at all to do with your web server, not even a little bit. The MX is *only* used by SMTP servers to find where mail should be delivered for your domain. Nothing else.

> let s say we have another web application that can use the same ports.

For the other sites, you must either use a different IP address, e.g.

site1.mycompany.com  A  62.62.63.65
smtp  A  62.62.63.64
Owamail  CNAME  SMTP.mycompany.com

Or a different port, or you must implement Host Headers on your website which lets the web server figure out the difference (can be done for HTTPS too, but is complex). None of those are Exchange specific, none use the MX.

Chris
0
 

Author Comment

by:jskfan
Comment Utility
OK ---
I will take it this way :
MX has nothing to do with OWA clients...
correct?
0
 
LVL 70

Assisted Solution

by:Chris Dent
Chris Dent earned 334 total points
Comment Utility
Correct.

Chris
0
 

Author Closing Comment

by:jskfan
Comment Utility
thank you guys!
0

Featured Post

Too many email signature changes to deal with?

Are you constantly being asked to update your organization's email signatures? Do they take up too much of your time? Wouldn't you love to be able to manage all signatures from one central location, easily design them and deploy them quickly to users. Well, you can!

Join & Write a Comment

Utilizing an array to gracefully append to a list of EmailAddresses
Exchange server is not supported in any cloud-hosted platform (other than Azure with Azure Premium Storage).
To show how to generate a certificate request in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.:  First we need to log into the Exchange Admin Center. Navigate to the Servers >> Certificates…
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…

772 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

Need Help in Real-Time?

Connect with top rated Experts

14 Experts available now in Live!

Get 1:1 Help Now