The local AD domain is named after company.loc, not company.local. So it is possible?

Question

Domain Name System

Good afternoon! There is a small Active Directory domain (about 50 users/computers, 30 printers), so far there is only one controller, OS Windows Server 2008 R2. I didn't do it, I got it ready-made. I myself am only studying AD, slowly :)

Actually, the question is this: previous system administrators called the domain, once upon a time like this: <domain name>.loc, not .local and something else. Works norms, pah-pah :)

Tell me, is this correct?

The fact is that recently, a new colleague, a system administrator, with extensive experience, was hired, and he claims that this is categorically wrong - we need to remake it on company.local (we plan to recreate the domain, due to modernization, since it is small and local) . He explained why, but somehow chaotically and somehow I clearly did not understand,how is *.loc worse than *.local?

I didn’t find an answer in Google, on Habré either, on the contrary, they say .local is already called non-comme il faut., For example, .nn or the like is better. But rather, about public domains, we don’t have such a thing yet, the domain is exclusively local ... I

apologize in advance for the possible stupidity of the question, my knowledge of AD is still minimal :)

UPD : Colleagues, thank you all for your answers! I chatted with my partner - he says he has been using the * .local domain in his office for 20 years - no problems. Well, as they say, everyone has their own experience! But I decided for myself that I probably won’t use *.local in my practice :)

Answer 1

Even better because there are problems

Answer 2

The .local zone is reserved for zeroconf and it is not recommended to use it, it's good that you have .loc .

Answer 3

it will still
overflow from empty to empty

Answer 4

Generally don't care. A site with an autumn name.loc is no worse than name.local. It's just a different domain ... either give the admin a pension or he is "faking" somewhere about the experience

Answer 5

IMHO, loc is the worst option, local is at least reserved. In general, according to the recommendations, you need to register, but you need to understand that in this way you bind your network to a public domain, the probability of changing which is incomparably greater than the .local domain.

Answer 6

Well, you can start with a short rfc or a little longer

Answer 7

It is better to choose a real domain that you have bought, then you want to get a real certificate and get it, neither local nor loc will allow you to do this. You will live forever with your own CA, there are many restrictions in this

Answer 8

Colleagues, a huge thank you to everyone for the answers!
If I understand correctly, then neither *.loc nor *.local is a cake, but *.local is clearly not worth using in 2021, but *.loc somehow, at the very least, will do.
I’ll talk about this with a colleague, thanks to you I now have arguments :)
Still, I ask you to share in the end what would you call the new AD domain, now in 2021?
As I understand it, the most "best practice" is to make a subdomain like corp.company.com? In general, I really like this option, we have had a website for a long time, and a corporate mail too. Seems like a logical progression...