Is the domain .Local a real problem in a private lan that has no public facing services?
-
I have a client that is going through a transition. They need a new server right now and their current domain is a .Local domain.
In short order, they will be consumed by another company and will be migrating their workstations to another (proper) domain.
Is it really so bad to bring up the new server on the existing .local domain and transfer all the FSMO roles to it and keep everything the way it is for now? I just don't see the hardship or problems with this since it is all internal anyway....
-
@JasGot no, it's fine. Almost nothing ever uses that and it was best practice for a long time.
-
Nothing in the Windows world uses it. Mac uses it, and some isolated Linux stuff. Really minor in most cases.
-
@scottalanmiller said in Is the domain .Local a real problem in a private lan that has no public facing services?:
Nothing in the Windows world uses it. Mac uses it, and some isolated Linux stuff. Really minor in most cases.
That what I had read also. Thanks. They are keeping .local during the transition!
-
@JasGot said in Is the domain .Local a real problem in a private lan that has no public facing services?:
@scottalanmiller said in Is the domain .Local a real problem in a private lan that has no public facing services?:
Nothing in the Windows world uses it. Mac uses it, and some isolated Linux stuff. Really minor in most cases.
That what I had read also. Thanks. They are keeping .local during the transition!
If it causes any problems (unlikely), there are workarounds too. It's never a show stopper.
-
@scottalanmiller What's the best thing to use on green field networks that are private and have no public facing services?
-
@ElecEng said in Is the domain .Local a real problem in a private lan that has no public facing services?:
@scottalanmiller What's the best thing to use on green field networks that are private and have no public facing services?
Not AD.
