2 different networks under same domain

[Kevin Darcy]

I think your problem boils down to: how do I get different programs to use
different nameservers for resolution?

In some resolver implementations, one can control what nameserver one uses
for resolution. With the Net::DNS module in Perl, for instance, you can set
the "nameservers" member of a Net::DNS::Resolver object to whatever
nameserver(s) you want.

Other resolver implementations aren't quite so flexible. Worst case, you
could run the app in a special chroot() area, solely for the purpose of
forcing it to see a different /etc/resolv.conf file than the regular one.


- Kevin

darcy w. christ wrote:

> hi,
>
>   i'm having trouble understand how to setup my nameserver(s).
> Presently, i have two nameservers - one that represents an internel
> network (using reserved ip addresses) and another one which is
> representing the domain for the outside world on public ip addresses.
> One of the ways that i have dealt with this scenerio is to have the
> outside server resolve itself (ie. use resolv.conf) to point to the
> internal dns and the internal dns points to the outside dns and beyond.
> This enables me to sit on the outside machine and see both networks
> under the same domain.
>
>   my problem is that i have two different programs running on the
> outside machine.  One requires the resolv.conf file to point to itself,
> while the other program requires that it point internally (so that it
> can resolve the internal network).  So, what i am wondering is whether
> this is a better way to do what it is i am doing.  i hope i being
> clear.  Basically i would like the external machine to be able to
> resolve any machine on this domain, whether it is on the internal or the
> external network, without publishing the internal network to the world.
>
>   i appreciate any thoughts or advice on the matter.
>
> --
> ~darcy w. christ
> Elegant Communications Inc.
> 416.362.9772 x222 | 416.362.8324 fax