Hello
we have a parent domain xxx.com.
we have create a childdomain child.xxx.com.
now i have a DNS problem:
the child.xxx.com was a secondary dns zone.
All DNS zones need both a Primary and optional
but important Secondaries (or equivalent*) sufficient
for performance and fault tolerance purposes,
including dealing with important WAN locations.
*An AD Integrated "set" of DNS-DCs can replace the
Single traditional Primary, and function with or without
additional secondaries.
Every zone has it's own set of servers, the Primary or
equivalent being REQUIRED at a minimum.
By definition there was a Primary for that child zone
at least when you create the zone, so either correct it's
problems or switch a child secondary to become Primary.
But the child.xxx.com was not in the same location as the parent
domain.
DNS routes so techically locations don't always matter
for DNS, but it is a good idea to have additional Secondaries
(or perhaps better AD Integrated) DNS servers wherever
you have separate significant locations, generally where you
have DCs.
I need a GC on the child domain.
Technically GCs don't have anything DIRECTLY to do with
Domains (except that they must run on SOME DC which is
by definition in some domain) but rather are a FOREST
resource.
You should place your MINIMUM number of GCs by
Site -- every Site needs as least one, two for fault tolerance,
and more when performance of network applications such
as Exchange is an issue (Exchange uses the GC in place of
its older "Global Address List" or GAL).
Any DC can be made a GC (with some very trivial restrictions
for keeping the Infrastructure master and GC apart in multi
domain setups UNLESS you make every DC in the domain a GC.)
If you have a SMALL multidomain forest you can make every
GC a DC usually and this may frequently be best -- generally a
single domain forest should have every DC a GC.
http://support.microsoft.com/?id=255248
=> no GC, GC just in the Parent Domain.
Are there any possibilites?
Add GCs by going to Sites and servers and selecting a DC,
expanding its "NTDS" properties and "checking the box".
Wait for replication.
BTW, it is a good idea to run DCDiag on every DC and
ensure that you have both full replication and correct DNS
replication for the plethora of DC records through the
Forest.
--
Herb Martin, MCSE, MVP
Accelerated MCSE
http://www.LearnQuick.Com
[phone number on web site]
thanks