Hiya, We have recently moved to a split DNS setup where our external domain is hosted internally. I have then added the same A records to this zone as can be accessed externally (mail.domainname.com for example). So I am now thinking about pointing Outlook clients to this 'zone', mail.domainname.com instead of theinternal FQDN of Exchange server, however Outlook always re-resolves to the internal FQDN when configuring the profile. Is it safe to change the info via Powershell, for example I can see the following values that use the internal FQDN; Fqdn, AutoDiscoverServiceCN, AutoDiscoverServiceInternalURI, RPCClientAccessServer I don't think FQDN can or should be changed, but the other 3 should be OK no? Thanks

You can change the internal services to point at the new address. You can have a look at this article by Elan Shudnow, it is made for Exchange 2007, but it should work for Exchange 2010 as well. Don't mind the title, but it describes what you want pretty good if I understand you correctly. http://www.shudnow.net/2007/08/10/outlook-2007-certificate-error/ /MartinExchange is a passion not just a collaboration software.

Thanks, but does not work. Following that document still results in internal Outlook client resolving to the internal FQDN of the mail server. I need Outlook to resolve to mail.domainname.com, and our Exchange server's FQDN is sev-ex01.corp.domainname.com. Do the changes in that article need services to be restarted? Thanks

I just checked the MS KB and found this one: http://support.microsoft.com/kb/940726/en I know it is still about certificates, but it does tell you how to change the internal URL for autodiscover, webservices and OAB, it also tell you to recycle the exchange application pool. /MartinExchange is a passion not just a collaboration software.

Besides above article, I would like to share you the following article to configure certificates and service URLs. http://msexchangeteam.com/archive/2007/04/30/438249.aspx Thanks.Novak Wu-MSFT

I have done all those things though, but Outlook persists on using the NetBIOS name of the server when creasting Outlook profiles. I will post output of the PS commands a bit later.