Only 1st Child DC to be built is visible in Root AD Sites & Servic

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Original Message:

When I build a new child domain, only the first DC to be
built is registered in the Root domain AD Sites &
Services. The Server has a NTDS Settings container
underneath it but it doesn't build any 'Automatically
Generated' connections. If I then try to check the
replication topology, it returns the following message:

The following error occurred during the attempt to contact
the domain controller: The Active Directory property
cannot be found in the cache.

This has only happened in two locations out of ten so I
guess it isn't a problem with the root.

Any help is appreciated.

Reply: (to Paul Williams questions)

Thanks for your response Paul...

Both of the DC's in the new Child domain are DNS servers for the delegated
namespace. They can both resolve the root DC's and vice versa. DNS Forwarding
is set up for anything that isn't in their namespace.

The relevant records are registered in (local) DNS i.e. SOA, NS, Host,
Kerberos, Ldap, & Kpasswd.

The relevant records are registered in the root DNS i.e. NS records in the
delegated domain, and GC & CNAME records for both servers.

This has only happened in a small number of sites but the same procedure has
been used to build each child domain so it doesn't really make sense.
 
That error is usually because of an erronous call to an LDAP server, i.e. a
typo in a script, etc.

Where are these machines pointing for DNS?

Could it be there's a typo in the IP address?

Perhaps you're pointing to the parent DNS server, not the delagated DNS
server? Remember that you often delegate a created zone with records in it.
Once that zone is delegated, only an authorative server can write to the zone.


--

Paul Williams

http://www.msresource.net
http://forums.msresource.net
 
Back
Top