Here's a fun one that hopefully someone can give me a hand with.
2008 R2 servers, Exchange 2013.
three years ago setup internal domain as M***.com. Email was hosted on web under their domain of M****acceptance.com with all their emails as such. Fast forward to January this year. Setting up Exchange 2013 on system, external (Internet facing) is mail.m****acceptance.com, but the internal names are still mail.m***.com. We don't own the m***.com domain but there is no mail.m***.com operating either, which was a lucky break. Our security certificates cover the m***acceptance.com domains, but can't cover the m***.com domain since we don't own it. I have pretty much worked around the security certificate mismatch warnings since the only thing wrong is m***.com is not on the certificate.
So I thought, why not just go through and rename the domain (all the desktops are virtual on one of the servers) since it primarily affected the servers. Wow, all of a sudden red flags everywhere about not renaming domains, but I found a bunch of conflicting ways to handle this issue.
so what I am asking is, how do I change the internal domain with an Exchange 2013 server on it, to a name that the Exchange server is already using for communications (m***acceptance.com). mail.m***acceptance.com is already a resolved FQDN on the internet.
So, if I am successful in changing the internal domain, it will stop the 200ms TCP latency between the servers because of the constant security certificate issues, and smooth operations since I won't have two different domains to mess with on the same server (external and internal).
Paul Clemmons, Owner, MCP PC Networks Inc MPN