Thanks! I will run this past our DNS guys. Will the users still be able to access their mail when using VPN to connect to the network?
On Mon, Jun 22, 2015 at 1:05 PM, Michael Pope <[email protected]> wrote: > Yes, but you only need to create an internal DNS forward lookup zone for > the actual external URL used to access Exchange. If you use multiple > external URLs, you would need a separate internal forward lookup zone for > each. This allows you to repoint to the internal IP address(es) only those > external DNS names that are necessary. All other DNS names within the > external DNS domain would still be resolved by your external DNS host. > Then, you would need to copy your external Exchange URLs to your internal > URLs. > > Michael > > > > On Mon, Jun 22, 2015 at 12:39 PM, Richard Stovall (RDI) < > [email protected]> wrote: > >> Split brain DNS, as much as Ben hates it, may be your answer here. >> >> >> >> *From:* [email protected] [mailto: >> [email protected]] *On Behalf Of *Candee >> *Sent:* Monday, June 22, 2015 12:21 PM >> *To:* [email protected] >> *Subject:* [Exchange] Fwd: Internal / external certs >> >> >> >> Hi everyone. >> >> I am updating our Exchange certificates, and we can no longer use our >> internal .local. >> >> There are no plans to change our AD; so I'm trying to find the best way >> to do this. >> >> >> >> If I just point our internal EWS, etc, to the external URL, is that going >> to work? >> >> I found a few posts that say yes; but a few that say that Outlook >> Anywhere will stop working. >> >> >> >> Anyone have any experience with this one? >> >> Hints? >> >> >> >> Thanks!! >> >> Candee >> >> >> > >
