Msdcs Domain Local Zone

Right click forward lookup zones in and select new zone.

Msdcs domain local zone. Either forestwide or domain wide or any other custom chosen list of dcs. Right click on the msdcs zone folder and delete. Follow steps to create an msdcs delegation on our primary server as outlined in the link in my initial post. Use that wizard to create the new zone.

Allow integrated forward zone on dc 3 to replicate. Could it be that the huge logging time is due to having 2 forward zones. Change replication scope on our primary forward dns zone to domain. Msdcs and domain controller location.

Name new zone msdcs testdomain the domain should be in full dns name of your ad domain. Is it safe to remove the msdcs zone. Open dns console right click forward lookup zones click new zone please select primary zone and check store the zone in active directory on the page of zone type and click next and again next. Steps to rebuild the msdcs dns zone.

Use the wizard to create the zone. The zone will now replicate to all other dns servers in the replication scope by using the replication schedules and paths that are configured in the forest or you can force replication. I checked dns to find that there are 2 forward lookup zones in the dns settings one with msdcs domain local and one with domain local. For example if your domain is named mydomain local name the new zone msdcs mydomain local.

Name the new zone msdcs domain where domain is the full dns name of your ad domain. To illustrate if i create a domain called parent local and a child domain called child parent local those domains will each contain a subdomain. Repeat steps 2 4 for each of our reverse lookup zones. Msdcs parent local and msdcs child parent local respectively.

In the domain local zones there is a subfolder with msdcs with fqdns.