Concerns creating .com domain along side same-named .local domain

I've been tasked to build a .com domain (customer facing and internal) to coexist for a time, with a forest trust between the two, with our current .local domain as we migrate over (obviously internal ntk).  The intent is to purchase a .com cert and slowly migrate our entire network from .local to .com domain.  we are currently at 2008 R2 domain and forest level, with a mix of 2012 and 2008 R2 servers.

we currently have numerous zones in AD as well, one of them is company_name.com as well already - servicing our external clients.

my question is what are the concerns, pitfalls, gotchas, is it wise to have a forest trust between a .com and .local with the same domain name, etc.

never had this scenario, and need some information/guidance on how to proceed.  so please don't assume anything.  and thanks in advance.
Jody DavisSystems EngineerAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Chris DentPowerShell DeveloperCommented:
There's no problem with the trust as long as your NetBIOS domain name also differs.

The most significant pitfall of using something.com for both public and private is that you can only control some of the DNS records on the private side. AD requires full ownership of certain records, one of those is the A records assigned to something.com.

Most of the guidance these days recommends the use of a private sub-domain of the public name. e.g. internal.something.com. It's long been my favourite suggestion. This frees the parent domain from conflict.

Chris
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Jamie McKillopIT ManagerCommented:
Hello,

My recommendation is that you use split-dns, especially if you are using Exchange. With split-dns, you have two separate zones for your .com. You would have an AD integrated zone and you would also have the zone setup on separate public-facing DNS servers. On the internal zone, you can use private IPs. This is also more secure as you wouldn't need to allow public access to your domain controllers. The only disadvantage is that you need to manage both zones separately.

-JJ
0
Aaron TomoskySD-WAN SimplifiedCommented:
+1 for something.domain.com

Corp, internal, int, i, cityname are all good examples of active directory private subdomain.
0
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

Pramod UbheCommented:
should not have any issues since .com and .local are two diff. things. please make sure to consult with your exchange admin for the org. name used in exchange or email addresses. additionally you have a very good opportunity to overcome existing challenges with new .com domain and plan wisely to accommodate changes/requirements that may come for next 5-10 years.

I would recommend to implement a new namespace with .com and implement whatever your plans are and then migrate existing .local namespaces to it.
0
Jody DavisSystems EngineerAuthor Commented:
thanks guys - here's the situation that they want to have me do.  my domain currently is mydomain.local, and they want to have mydomain.com - both would have the NETBIOS name the same - mydomain - have a CAS server in the .com to work with exchange for the moment - and have a trust between the two.

1. is having the NETBIOS name "mydomain" (made up of course) the same for the existing .local and the new .com ok regarding the trust, exchange and a certificate planned for the .com domain now that we have to abandon .local these days?

2. will exchange work in this regards?
0
Jamie McKillopIT ManagerCommented:
You can't create the trust if the NETBIOS names match. Also, you can't just bring up a CAS server in another forest.

-JJ
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Active Directory

From novice to tech pro — start learning today.