AD domain .local?

Question

Active Directory

Why is this bad and what problems can it cause?
From what I found: .local is used in Zeroconf - but this is for home networks, and in theory there should be no problems.

Answer 1

There the question is “how is it better”, but what’s wrong with me is .local (I already have it). So far, I have not heard a single sane answer - except for "more convenient." It’s quite convenient for me with local too - what should I do now, because of this little thing, reconfigure everything?

Answer 2

They just raised the question of what to produce entities - habrahabr.ru/qa/13050/#answer_55760

Answer 3

For themselves, they came to the conclusion that it is much more literate, and most importantly, easier, to use a domain consonant with the main postal address or website of the organization.
There will be no confusion:
- Dial mail dot, maycompany, dot, locale.
- RU?
- Local!
If there are many affiliates with different names, then you can make a single domain, and within its framework assign names to resources.

Answer 4

I don’t see any fundamental problems with using .local, so it’s not bad at all. In principle, you only need to follow the rule of non-matching with existing top-level domains, otherwise you are free.

Answer 5

.local is bad only in one situation - if you decide to start using cloud services (like a Office365) from a purely internal closed network, or access your domain via the Internet.
You won’t get an SSL certificate for a fictitious domain, and renaming the domain and then running the changes on that mountain of services that you have already configured on .local over the years of work will be a hell of a lot.
So do it right from the start, don't use .local, .corp, .lan, etc. and even more so, single-level domains.