Namespace design consideration for Exchange Server 2016 coexistence

People,

I need some help and explanation as to why I need multiple different name spaces for Exchange 2010-2016 co existence ?

With an Exchange 2010 site-resilient design, you needed up to eight different namespaces:
two Internet Protocol namespaces
two for Outlook Web App fallback
one for Autodiscover
two for RPC Client Access
one for SMTP.

My AD domain is just single forest domain.com so what are the best suggested name to choose ?
LVL 9
Senior IT System EngineerIT ProfessionalAsked:
Who is Participating?
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.

Jamie McKillopIT ManagerCommented:
Hello,

With multiple sites, the first decision you need need to make is are you going to use bounded or unbounded namespace? With an unbounded namespace, you use a single name for all your sites and use DNS round robin. This has the advantage of provide automatic fault tolerance if a site goes down. The disadvantage is that your traffic is going to be random. A user with a mailbox is Site A may connect to a CAS is Site B. Due to this, you need to unsure you have adequate bandwidth between your sites.

With a bounded namespace, each of your sites uses a different name. The advantage to this is that you control traffic. Users with a mailbox in Site A always connect to a CAS in Site A. This is good if your bandwidth between sites is limited or the site connection is unreliable. The disadvantage is that if you have a site goes down, it is a manual process to perform a data center switch over.

The next decision you need to make is are you going to use split-DNS, where you use the same name internally and externally or are you going to use different internal and external names. Split-DNS used to be the preferred method but there is a problem with using split-dns in Exchange 2013/2016. If the internal and external names are the same for Outlook Anywhere, the authentication method for the internal name will always be used. This means you can't have Kerberos or NTLM set for internal authentication and Basic set for external.

So, the fewest names is if you use an unbounded namespace with split-DNS. In that case you would need:

mail.domain.com
autodiscover.name.com

With bounded namespace and split-dns, you would need:

mail1.domain.com
mail2.domain.com
autodiscover.domain.com

With unbounded and non-split-dns:

mail.domain.com
mail.internaldomain.com
autodiscover.domain.com

With bounded and non-split-dns:

mail1.domain.com
mail2.domain.com
mail1.internaldomain.com
mail2.internaldomain.com
autodiscover.domain.com

-JJ
1

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
Will SzymkowskiSenior Solution ArchitectCommented:
This really comes down to DNS configuration. How do you currently have your DNS namespaces setup for your Exchange environment? How many internet facing Sites do you have? Can you also provide the resource that illustrates what you are talking about?

Also have a look at the Exchange Server Deployment Assistant which will help guide you through the process.

Exchange Server Deployment Assistant
https://technet.microsoft.com/en-us/office/dn756393.aspx

Will.
1
Senior IT System EngineerIT ProfessionalAuthor Commented:
This really comes down to DNS configuration. How do you currently have your DNS namespaces setup for your Exchange environment?

It is hosted internally by Windows Server AD integrated.

How many internet facing Sites do you have?

1 in the Data Center only.

Can you also provide the resource that illustrates what you are talking about?

I need to plan for which SSL certificate to renew or buy with this new upgrade.
0
Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

Senior IT System EngineerIT ProfessionalAuthor Commented:
ok, can I use the minimum name space as follows:

mail.domain.com --> for OWA, SMTP, Activesync, Outlook client
autodiscover.name.com -->first time lookup for Outlook and ActiveSync I guess ?

Note, I  am planning to use Citrix Netscaler VPX appliance as the load balancer.
0
Jamie McKillopIT ManagerCommented:
Yes, you can use just two hostnames provided you are using split-DNS and an unbounded namespace.

-JJ
1
Senior IT System EngineerIT ProfessionalAuthor Commented:
Thanks !
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
Exchange

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.