DNS Domain Delegation.......

[Kevin Darcy]

Are you using an internal root, or the Internet root? If you're using an
internal root, then you can just delegate "adroot.com" from your internal root
(or your internal ".com" if you have one).

If you're using the Internet root, then you're going to have to "override" this
view of the Internet namespace by defining "adroot.com" explicitly on all of
your nameservers (as master/slave/stub/forward).

By the way, "adroot.com" is a poor choice of domain, since it's already
registered on the Internet. What if you ever want to send mail (or whatever) to
the *real* adroot.com? You should either register some real domain on the
Internet for this purpose, or use an illegal TLD so that you will never collide
with an existing Internet domain, e.g. adroot.local or adroot.internal.


- Kevin

rengland wrote:

> I'm faced with a problem I'm hoping to get some help on.
> The client that I am at, is currently in the process of deploying Windows
> 2000 AD, we use QIP to manage the entire DNS environment, except for the
> Windows 2000 AD. All client are registered in QIP and point to QIP DNS
> server for named resolution. The Window 2000 AD DC's register in the W2K DNS
> servers and we delegate to those DNS servers from QIP.
>
> Example, "foo.com" exists in QIP, but "wins.foo.com" and "exchange.foo.com"
> and "abc.foo.com" exist in the W2K DNS servers. In the db.foo.com zone file
> we have delegated to the W2K DNS servers.
>
> This is ok, but now the W2K team wants a new top level domain to accommodate
> their AD root domain, for the Global Catalog. The new domain they setup in
> W2K is "adroot.com", and they want us to Delegate to "adroot.com". Other
> than setting up a delegation at the ".com" domain or making our QIP DNS
> server secondaries for the W2K DNS server I'm not sure if there is another
> option.  I'm looking into Stubs, etc.
>
> Any Ideas, or help would be great!!!
>
> Thanks,.....Robert C. England