I have a PDC (which also is a DNS Server) and several servers with DBs in
remote locations; I want to promote those servers to BDCs and make them DNS
servers, as well. I have a question regarding which name should I assing to
the stub zones I want to create in the new BDCs? Is is mandatory to name all
them as my domain name (the DNS wizard recommends it and some other
tutorials)? Would be some problem if I have 15 DNS with stub zones named all
the same?

"Abraham" <Abraham@discussions.microsoft.com> wrote in message
news:1520E05D-9CB5-4883-9D68-454979EF635A@microsoft.com...
>I have a PDC (which also is a DNS Server) and several servers with DBs in
> remote locations; I want to promote those servers to BDCs and make them
> DNS
> servers, as well.

[It's just DCs in Win2000+ (no PDC or BDC).]

> I have a question regarding which name should I assing to
> the stub zones I want to create in the new BDCs? Is is mandatory to name
> all
> them as my domain name (the DNS wizard recommends it and some other
> tutorials)?

A Stub zone MUST be named for the zone it is stubbing;
it is in fact quite similar to a Secondary, almost identicial
except in that it doesn't transfer ALL of the records but
merely enough (SOA, NS+A for nameservers) to be able to
FIND all of the records.

Since they are remote locations one would expect first cut
that you would use AD_integrated (at some point) when you
make these DCs.

> Would be some problem if I have 15 DNS with stub zones named all
> the same?

If they are for the SAME ZONE that is the only choice -- if they
are for some other zone then they must be named for that zone.

There is no issue about "how many" and no real choice about the
name of a Stub, or Secondary DNS zone since it must be FOR some
existing zone.

--
Herb Martin, MCSE, MVP
Accelerated MCSE
http://www.LearnQuick.Com
[phone number on web site]