Domain Name .local

Please check this to make your internal and external name the same and get rid off certificate errors
https://www.experts-exchange.com/articles/13676/Out-Of-office-not-working.html

I would like to switch the current private network anydomain.local to anydomain.us which is the registered name. The links you provided do not offer any help with that. I need to mention that Exchange has NOT been installed on this domain yet.

My last post was a reply to Zach.

But won't this cause trouble with setting up Exchange?

No it will not create problem for Exchange servers as the recommended way to access OWA,ECP etc is to use external name instead of using internal FQDN in all the new versions of Exchange servers.

You can make both internal and external URLs the same using this

Yikes, that last one just blew me away. If you guys were setting this up, what would you use for the internal name?

Again, Exchange has not yet been installed.

if you have .us domain controller in place then just disjoin your computer from .local domain and re-join in US domain. thats all you need to do.

The controller is currently anydomain.local

so you are good to go .... just install Exchange and add .us domain in accepted domain.

Once you are done then publish your all DNS URLs with .us only. also you will have to use .us URLs certificate.

Create an e-mail address policy using .us domain only. this architecture will definitely work.

It depends on you now if you create .us DNS internal and external both or you just ok with using .us URLs from internet in internal and external both networks...

Here is a write up,
http://social.technet.microsoft.com/wiki/contents/articles/17974.active-directory-domain-naming-considerations.aspx
what is the issue that you think is an obstacle?

One thing I would not do is rename it to the public domain.

You having just got into .., you are asking the wrong people, you should ask those whose server/setup it is whether they would consider such a change with you providing the reasoning behind it.

Presumably when one gets into addressing/setting someone elses existing, they need to work with what those individuals have.  The first thing to them should not be hey, we need to change this or that, the systems you got are this or that, you need to get new ones, etc.

The rename of a domain is fairly straight forward depending on the type, the renaming might be limited and are you willing to put yourself without seemingly understanding their environment.  The change you want to make is only because the public certificate will not be issued with a .local SAN host names for a single application, exchange, is not a sufficient reason to upend whatever the existing setup is.

there are many organization those never use external domain name in their internal domain. even I am working with an org. and we don't use external domain as our domain controller's domain name. we have diff. one and there is no issue using like this as you can segregate it easily. Exchange has functionality to accept domain and you can use e-mail address policy to assign specific domain's e-mail address and definitely .local domain will not be a certificate name that is why .com or .us will be domain's certificate.

So if I leave it as .local I will not have any issues with certificate?

Is certificate the inky and priMary impediment that you see? Let's say the firm has multiple domains anydomain.us, anydomain.com, anydomain.info and they got you to setup their exchange such that each domain have their own respective hostnames for inbound/outbound. Would that be a problem?

The certificate is the least important in my opinion.

Agree certificate is least important. you can create certificate as per your convenience it is in your hand.

Thank you