Hi All.
We are currently using just Exchange 2010 with a view to migrating to Exchange 2013
I have read all the recent blogs (specifically from Brain Day) relating to CAS; these include ‘Demystifying the CAS Array Object’ and the very interesting ‘Ambiguous URLs and their effect on Exchange 2010 to Exchange 2013 Migrations’
I now know that Outlook must always use Outlook Anywhere (RPC over HTTPS) to function correctly with Exchange 2013 both internally and externally.
Therefore Outlook has to be able to resolve 'mail.contoso.com' to a public address for external users to hit the Outlook Anywhere proxy URL, (as it currently does for us), and an internal address for network (LAN) users
Here’s my question…
We use external DNS servers at our ISP for Internet users to resolve our public facing servers, for example (I've replaced our real domain name with ‘contoso’): -
mail.contoso.com (for Outlook Anywhere)
www.contoso.com
ftp.contoso.com
Internally our AD Forest is ‘company.contoso.com’ so we use Active Directory DNS Servers for all internal name resolution, for example: -
outlook.company.contoso.com (for MAPI Outlook)
server1.company.contoso.com
server2.company.contoso.com
How do I ensure that Outlook Anywhere resolves ‘mail.contoso.com’ to an internal address when clients are on the LAN?
Can I add a ‘contoso.com´ zone to our Active Directory DNS Servers to solve this, without affecting any AD or DNS (Internal and External) functionality?