[Webinar] Streamline your web hosting managementRegister Today

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1119
  • Last Modified:

Greyed out _msdcs container under my dns domain

I had one Windows 2003 DC running DNS and DHCP  (London-DC1) , recently I added two new Windows 2008 Domain Controllers with DNS (London-DC2 and London-DC3). Currently my DNS zone looks like following

--Forward lookup Zone
  _msdcs.treaty.local

            ---- London-DC1  (ns server)
            ---- London-DC2  (ns server)
            ---- London-DC3  (ns server)

-- treaty.local

      -- msdcs  (this container is greyed out)

                  ---- London-DC1  (ns server)

Question is why the greyed out _msdcs container has only one ns server record. Should there be 3 ns records or just 1 ns records? And why?
0
adding7
Asked:
adding7
  • 2
1 Solution
 
footechCommented:
The grayed-out _msdcs is a delegation.  These don't update automatically.  You likely wouldn't see any issue if you just have a single domain with the delegation as is.  It's best though to have the delegation point to any name servers that have the _msdcs zone (which is usually replicated to all DNS servers in the forest).
0
 
adding7Author Commented:
thanks for the update, just one quick question regarding this.....   I understand I can create this manually.

Shouldn't  this delegation records gets created during dcpromo - when I installed 2 new dc's?

Also authorative DNS server is London-DC2
0
 
footechCommented:
No, the delegation gets created when you first set up a domain, but other than that it is a manual process to update it.
0

Featured Post

Never miss a deadline with monday.com

The revolutionary project management tool is here!   Plan visually with a single glance and make sure your projects get done.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now