ML
    • Register
    • Login
    • Search
    • Recent
    • Categories
    • Tags
    • Popular
    • Users
    • Groups

    Solved What to use for new Windows network domain

    IT Discussion
    windows server 2022 domain controller
    6
    13
    231
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • JaredBusch
      JaredBusch last edited by

      New site going in clean. All old stuff getting pitched.

      It will be a local Windows DC.

      What are people using today for the domain?

      Is ad.domain.com still in fashion?

      Something different?

      dbeato scottalanmiller J 3 Replies Last reply Reply Quote 0
      • Topic has been marked as a question  JaredBusch JaredBusch 
      • J
        JasGot @JaredBusch last edited by

        @JaredBusch
        We use ad.domain.tld
        No need for split DNS this way.

        JaredBusch 1 Reply Last reply Reply Quote 1
        • dbeato
          dbeato @JaredBusch last edited by

          @JaredBusch I have been using ad.domain.com since it is up to code based on Microsoft's recommendation.

          JaredBusch 1 Reply Last reply Reply Quote 2
          • JaredBusch
            JaredBusch @dbeato last edited by

            @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.

            1 Reply Last reply Reply Quote 0
            • F
              flaxking last edited by

              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

              https://learn.microsoft.com/en-us/azure/active-directory-domain-services/tutorial-create-instance#create-a-managed-domain

              dbeato 1 Reply Last reply Reply Quote 0
              • dbeato
                dbeato @flaxking last edited by

                @flaxking That would be for Azure Active Directory not Active Directory.

                F 1 Reply Last reply Reply Quote 1
                • F
                  flaxking @dbeato last edited by flaxking

                  @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.

                  dbeato 1 Reply Last reply Reply Quote 0
                  • Pete.S
                    Pete.S last edited by

                    I think corp.contoso.com makes 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

                    1 Reply Last reply Reply Quote 0
                    • scottalanmiller
                      scottalanmiller @JaredBusch last edited by

                      @JaredBusch said in What to use for new Windows network domain:

                      Is ad.domain.com still in fashion?

                      This is what we use.

                      1 Reply Last reply Reply Quote 0
                      • dbeato
                        dbeato @flaxking last edited by

                        @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.

                        F 1 Reply Last reply Reply Quote 0
                        • F
                          flaxking @dbeato last edited by

                          @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.

                          1 Reply Last reply Reply Quote 0
                          • J
                            JasGot @JaredBusch last edited by

                            @JaredBusch
                            We use ad.domain.tld
                            No need for split DNS this way.

                            JaredBusch 1 Reply Last reply Reply Quote 1
                            • JaredBusch
                              JaredBusch last edited by

                              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.

                              1 Reply Last reply Reply Quote 1
                              • Topic has been marked as solved  JaredBusch JaredBusch 
                              • JaredBusch
                                JaredBusch @JasGot last edited by

                                @JasGot said in What to use for new Windows network domain:

                                No need for split DNS this way.

                                That is a huge reason.

                                1 Reply Last reply Reply Quote 1
                                • First post
                                  Last post