Configure Public DNS records for Exchange

My first question is what version of Exchange are you deploying? You have described an Exchange 2010 type deployment where the roles are separated out. On Exchange 2016, these roles now all exist on the same server. You have multiple servers for load balancing and DAG failovers, but roles such as transpoort, CAS, and mailbox exist on the same server. The only separate role is the Edge server. If you are installing Exchange 2010, why would you not install a newer version of Exchange like 2016?


We do not use the Edge role, but our MX record points to our spam filter appliance in the DMZ, not directly to the CAS server.

The MX record should point to the A record, which then points to your mail server. All of this should point to the external, static IP address provided by your ISP. The Edge server then communicates with the internal server for mail deliver. You should then have an internal DNS record for internal clients pointing to the server (CAS in the case above). Much depends on the features of your firewall. We use Netscalers with content redirection, so we can use the same external IP for about everything and use the headers to redirect the traffic to specific servers. However, if that is not available, the you can use another external IP for things like webmail and activesync that which use the same port (443), and on the firewall redirect that traffic directly to the CAS servers. In the case of Exchange 2016, the internal servers. Does this answer your question?

An A record for the Public IP of you Edge. this will be for SMTP only. You can call this record whatever you wish. I would also recommend, if you can, to see if your ISP can provide a PTR record for the IP in their reverse lookup zone. This helps with SPAM
An MX record referring to it.
Another IP that maps to your CAS servers or the Load Balancer VIP for them (not sure why you separated the roles but since you did, I assume this is Exchange 2013. Why not 2016?) Either way. that IP will bu used for Webmail and Autodiscover.
No, in this case, with an edge server, the MX and CAS will not point to the same name.

hello

Let me give you some precisions I am not the One who did the design . It Was another engeneer He did installed Exchange 2016 but He left 2 MBX/CAS as 'CAS Server' These servers do not have mailboxes . They are considered CAS Server

So this is my Setup attached Still setting Up is it OK?

Now I need autodiscover and mail pointing to the 'CAS SERVER' I guest i need another Public IP Nated to the CAS servers?
godaddy.png