non-authoratative domains

[Kevin Darcy]

One ugly way is to create a zone for each name, e.g. foo.xyz.com could be a
zone by itself. You could even set up one box as master for foo.xyz.com and
the others could be slaves, so that you only have to maintain that zone in one
place. If the number of such names grows large, then named.conf maintenance
becomes horrendous.

I guess I don't quite understand how you can have access to your extranet
partner's network for web access but *not* for DNS. Are they blocking
DNS queries from your network? Why? With "partners" like that...


- Kevin
injuntribe wrote:

> Is there a way to add an domain to your internal dns system without being
> authoratative for that domain?
> Or add cname records for a domain you do not serve dns for?
>
> I want to avoid using hosts files.
> Example:
>
> I own abc.com but my internal users need access to an extranet partners web
> sites via hostname / url (ip address will not get them to the correct web
> page).
> how can I add a few records to my dns for xyz.com without being
> authoratative for the entire xyz.com domain. (The extranet partner does not
> route or have dns entries for this address space on the internet, nor do we
> have acccess to their internal dns)
>
> Thank you,
> injun