New AD site, first DC/DNS server.

Hi,

We recently just setup a new subnet and site in AD "Sites and Services".

The VPN is up and I can communicate back and forth over the link to the other DC's (DC01 and DC02). I have setup the new server (DC03) and entered the DC01 and DC02 IP's for DNS.

Installed Active Directory Servers and DNS. The only prerequisite warning I got was

WARNING: A delegation for this DNS server cannot be created because the authoritative parent zone cannot be found or it does not run Windows DNS server. If you are integrating with an existing DNS infrastructure, you should manually create a delegation to this DNS server in the parent zone to ensure reliable name resolution from outside the domain "mydomain.biz". Otherwise, no action is required.

Select allOpen in new window

Now I continued through and all seems to be relatively well. Changed DC03's primary DNS to it's own IP.

However when I launch the DNS MMC for DC01 and drill down into the domain parent zone (DC01>Forward Lookup Zones>mydomain.biz) I can see all the DNS servers listed as nameservers but not my new one (DC03)?

When I do the same check on DC03 (DC03>Forward Lookup Zones>mydomain.biz) I can see all the DNS servers listed as nameservers, DC03 included.

Any ideas, do I need to manually add the delegation and if I do can someone give me specifics? I'm no DNS guru.

Thanks,