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

    DC DNS Settings

    Scheduled Pinned Locked Moved IT Discussion
    29 Posts 11 Posters 2.4k Views
    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.
    • BRRABillB
      BRRABill @scottalanmiller
      last edited by

      @scottalanmiller

      This is why I asked.

      See what I mean?

      Can we at ML come up with a best practice?

      1 Reply Last reply Reply Quote 0
      • thwrT
        thwr
        last edited by

        Looks like I got the question wrong 😉

        1 Reply Last reply Reply Quote 0
        • V
          Veet
          last edited by

          Always pointed it to itself, as the primary ... Also, doesn't Microsoft itself recommend this as a Best Practice ?

          1 Reply Last reply Reply Quote 0
          • BRRABillB
            BRRABill
            last edited by

            So, does it really seem like we're all doing it wrong?

            That DC1 should have DC2 listed as its primary DNS server? And DC1 secondary?

            brianlittlejohnB 1 Reply Last reply Reply Quote 0
            • brianlittlejohnB
              brianlittlejohn @BRRABill
              last edited by brianlittlejohn

              @BRRABill I have two DCS,
              DC1 has DC2 as primary and itself as secondary. Then for DC2, DC1 is primary and itself secondary.

              BRRABillB 1 Reply Last reply Reply Quote 0
              • BRRABillB
                BRRABill @brianlittlejohn
                last edited by

                @brianlittlejohn said in DC DNS Settings:

                @BRRABill I have two DCS,
                DC1 has DC2 as primary and itself as secondary. Then for DC2, DC1 is primary and itself secondary.

                Seems like that is what is now recommended. Though all the first few posters did not have it set up that way, and that is apparently not the way MS used to recommend.

                1 Reply Last reply Reply Quote 1
                • BRRABillB
                  BRRABill @BRRABill
                  last edited by

                  @BRRABill said in DC DNS Settings:

                  I do the same, itself as primary.

                  But it seemed like there were a lot of people on the Internet with the opposite.

                  Of course, they aren't the geniuses here at ML. 🙂

                  I take it back, my servers were NOT set up like this.

                  Not that anyone cares. Just wanted to set the record straight. 🙂

                  1 Reply Last reply Reply Quote 1
                  • DashrenderD
                    Dashrender
                    last edited by

                    I have been doing the Primary points to other DNS and secondary to itself for over 5 years, and probably more like 15.

                    BRRABillB 1 Reply Last reply Reply Quote 0
                    • BRRABillB
                      BRRABill @Dashrender
                      last edited by

                      @Dashrender said in DC DNS Settings:

                      I have been doing the Primary points to other DNS and secondary to itself for over 5 years, and probably more like 15.

                      Me, too. Never an issue.

                      I wish we could have figured out why MS seems to be recommending it.

                      1 Reply Last reply Reply Quote 0
                      • AdamFA
                        AdamF
                        last edited by

                        Adding to this:

                        I've also always point the primary to 127.0.0.1 and secondary to the secondary controller. If no secondary controller, then a public DNS.

                        BRRABillB 1 Reply Last reply Reply Quote 0
                        • BRRABillB
                          BRRABill @AdamF
                          last edited by

                          @fuznutz04 said in DC DNS Settings:

                          Adding to this:

                          I've also always point the primary to 127.0.0.1 and secondary to the secondary controller. If no secondary controller, then a public DNS.

                          Funny there are so many ways to do this that don't break it.

                          Reid CooperR 1 Reply Last reply Reply Quote 0
                          • Reid CooperR
                            Reid Cooper @BRRABill
                            last edited by

                            @BRRABill said in DC DNS Settings:

                            @fuznutz04 said in DC DNS Settings:

                            Adding to this:

                            I've also always point the primary to 127.0.0.1 and secondary to the secondary controller. If no secondary controller, then a public DNS.

                            Funny there are so many ways to do this that don't break it.

                            That don't break it.... right away.

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

                              So here is a quesiton. When you first add a secondary DC/DNS, do you go back to the original DC and update the DNS on the NIC? Or do you leave the original pointing only to 127.0.0.1?

                              1 Reply Last reply Reply Quote 0
                              • 1
                              • 2
                              • 2 / 2
                              • First post
                                Last post