Azure Directory Sync

We are currently using name1.local for our internal domain, our email is name2.com. We are moving to Azure and need to change it, so we are thinking to move it to name2.com to coincide with our current email addresses. In our current DNS we have name1.local and name2.com resolving to external IP's.
If we create a cross-function domain using name2.com is that going to cause us all sorts of grief with DNS?



It used to be recommended that you always have a separate DNS space for AD domains. This advice seems to have relaxed a little.

The main issue you will encounter is that unless you expose your AD DNS servers to the internet and use them as your internet DNS servers you will have to maintain your DNS in two places.

If you really want to use your .com internally consider using a subdomain, i.e. internal.name2.com. That way you get a degree of separation.



It used to be recommended that you always have a separate DNS space for AD domains. This advice seems to have relaxed a little.

The main issue you will encounter is that unless you expose your AD DNS servers to the internet and use them as your internet DNS servers you will have to maintain your DNS in two places.

If you really want to use your .com internally consider using a subdomain, i.e. internal.name2.com. That way you get a degree of separation.









Share this

Related Posts

There was an error in this gadget