Server side multiple domain search?

[Kevin Darcy]

Jerry Christopher wrote:

> "Mathias K=F6rber" wrote:
>
> [snipped my orig. question & No answer from Mark.Andrews at nominum.com]
>
> > If it is only supposed to be for domain somedomain.com, why not just
> > put foobar.somedomain.com into the DNS? AM I missing something here?
> > WHat other domains is it supposed to search if you limit the applicat=
ion
> > to one domain in the first place?
>
> What would be of interest to me is a server side option to search
> another domain without making any change to the client side.  Taking
> our two domains as an example, koerber.org and amcc.com.  A client in
> amcc.com could nslookup barney.  The internal NS, not finding it in
> amcc.com would also search koerber.org by forwarding the request
> directly to 203.127.219.241 (ns1.koerber.org).   If host barney was
> found, the request would come back and get cached at the internal NS
> at amcc.com.

It's the job of the resolver -- not the nameserver -- to come up with
"alternate" queries when the first one is non-productive.

> Is the closest thing to achieving this both a server side & client
> side change?  Set myhost.amcc.com resolv.conf search path to include
> koerber.org, then set the internal DNS server with a koerber.org
> forwarding zone specified as first to 203.127.219.241 ?

Why would your nameserver need to forward for koerber.org? Couldn't it be
found through the normal referral mechanisms?


- Kevin