Naming a domain in 2012 R2 Essentials

I've been reading a lot about not using .local domain names. I wondered what the consensus was here? I have a customer company.co.uk.

I was thinking about following the instructions here: http://www.em-soft.si/myblog/elvis/?p=403 and naming the domain on this new server as internal.company.co.uk. Is that recommended still today, or is company.local just as good?

Thought i'd check before i get too deep into the installation.
LVL 1
Coriron HazManaging DirectorAsked:
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.

LeoCommented:
According to MS naming convention guide....
https://technet.microsoft.com/en-us/library/cc738121(WS.10).aspx 

if you own company.co.uk, use ad.company.co.uk or you can use internal.company.co.uk as well.

The most vile thing, as I see it, is using the registered Internet domain name, verbatim, for the Active Directory domain name. This causes you to be forced to manually copy records from the Internet DNS (like www) into the Active Directory DNS zone to allow "external" names to resolve. I've seen utterly silly things like IIS installed on every DC in an organization running a web site that does a redirect such that someone entering company.co.uk into their browser would be redirected to www.company.co.uk by these IIS installations. Utter silliness!

Using the Internet domain name gains you no advantages, but creates "make work" every time you change the IP addresses that external host names refer to. (Try using geographically load-balanced DNS for the external hosts and integrating that with such a "split DNS" situation, too! Gee-- that would be fun...)

Using such a subdomain has no effect on things like Exchange email delivery or User Principal Name (UPN) suffixes, BTW. (I often see those both cited as excuses for using the Internet domain name as the AD domain name.)

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
Coriron HazManaging DirectorAuthor Commented:
ok. so just to confirm, if i use internal.company.co.uk, i wont have any issues resolving external addresses like www.company.co.uk?

It's only if i was to use the domain of company.co.uk as my internal domain that I would have issues?
Cliff GaliherCommented:
Essentials will append .local unless you jump through a bunch of hoops not to. I would honestly recommend just letting essentials do this unless you have a specific compelling apo that requires otherwise. There is no specific issue with .local on most domains. And that includes 99/999% of SMB that essentials targetsm
LeoCommented:
.local will work in most of the cases, or you can use .internal as well.
Do  you require any other assistance?
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
Windows Server 2012

From novice to tech pro — start learning today.