Solved What to use for new Windows network domain
-
@dbeato said in What to use for new Windows network domain:
@JaredBusch I have been using ad.domain.com since it is up to code based on Microsoft's recommendation.
That was what I used last time I did a greenfield Windows AD deployment. But that was like 6 years ago.
-
Well Microsoft's AAD DS recommendation has changed from aadds.contoso.com to aaddscontoso.com but I don't think they have really said why
-
@flaxking That would be for Azure Active Directory not Active Directory.
-
@dbeato yes, Azure Active Directory Domain Services. That documentarion changed from aadds.contoso.com to aaddscontoso.com. But since they don't give the reason for the change, it is unclear if the reason applies to both aadds and ad.
The only reason I know of is so that AD isn't displayed as the domain name in places.
-
I think
corp.contoso.commakes the most sense if you're doing split-dns. Then it doesn't matter if it's AD or AAD or whatever.Microsoft uses it often in their docs as well.
https://learn.microsoft.com/en-us/windows-server/networking/core-network-guide/core-network-guide -
@JaredBusch said in What to use for new Windows network domain:
Is ad.domain.com still in fashion?
This is what we use.
-
@flaxking Well the point was that Jared was making of a local network domain which Azure Active Directory wouldn't have counted but I understand.
-
@dbeato said in What to use for new Windows network domain:
@flaxking Well the point was that Jared was making of a local network domain which Azure Active Directory wouldn't have counted but I understand.
I wasn't talking about AAD, I was talking about AAD DS.
-
@JaredBusch
We use ad.domain.tld
No need for split DNS this way. -
I did go with
ad.domian.com. Just been so long sent I set one up new, I figured I would run it by everyone.Thanks for the feedback.
-
J JaredBusch has marked this topic as solved on
-
@JasGot said in What to use for new Windows network domain:
No need for split DNS this way.
That is a huge reason.
