Announcement

Collapse
No announcement yet.

DNS IPs in TCP settings

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • DNS IPs in TCP settings

    We have two domain controllers, each having the DNS role installed. What is the best practices for the dns entries in each dc's tcp settings?

    DC1:
    1: IP of DC1
    2: IP of DC2

    DC2:
    1: IP OF DC2
    2: IP OF DC1

    OR

    DC1:
    1: IP of DC2
    2: IP of DC1

    DC2:
    1: IP of DC1
    2: IP of DC2

  • #2
    Re: DNS IPs in TCP settings

    First option. Best practice is always for a DNS server's primary DNS server to be itself.
    BSc, MCSA: Server 2008, MCSE, MCSA: Messaging, MCTS
    sigpic
    Cruachan's Blog

    Comment


    • #3
      Re: DNS IPs in TCP settings

      And, to add to cruachan's response, and taken from a similar question I recently asked, the primary address should be 127.0.0.1 and not the static IP address assigned to the adaptor.
      A recent poll suggests that 6 out of 7 dwarfs are not happy

      Comment


      • #4
        Re: DNS IPs in TCP settings

        I'm pretty sure that the current best practice (although even Microsoft seems to have a difficult time determining what they recommend) is that a DC/DNS should point to another DC/DNS first and then to itself. It should also point to 127.0.0.1, but not as the first two.

        A DC (like any other AD client) needs to query DNS when it boots up in order to locate a DC. Because of the order of initialization (network card, DNS, AD DS, etc.) a DC pointed to itself first will often fail this lookup. In addition, a DC needs to locate it's replication partners when booting up in order to verify replication and to load AD DS. As a result you'll get spurious errors regarding loading of AD, DNS, Replication, etc. when a DC/DNS server points to itself or 127.0.0.1 first.

        Comment

        Working...
        X