2 different networks under same domain

[Adam Lang]

Yeah, apparently from what I read, v9 and views is eventually the way to go.
Why would you care to sort by program?

The "internal" nameserver/view will have all the internal names AND the
external names whereas the external nameserver/view will have ONLY the
external names.  A program on the internal network would have access to
everything whereas a program on the outside would only have access to what
you have on the exernal view.  Any reason why that wouldn't work?

As for doing it with v8.2.3, you can read up on split DNS or do it a way
mentioned in the bok I just read.  Have two versions of named running on
separate interfaces and have them both running under their own chroot jail.
Seems a bit compkicated, but also seems rather secure.

Adam Lang
Systems Engineer
Rutgers Casualty Insurance Company
http://www.rutgersinsurance.com
----- Original Message -----
From: "darcy w. christ" <darcy at elegant.com>
To: "Adam Lang" <aalang at rutgersinsurance.com>
Cc: "bind" <bind-users at isc.org>
Sent: Wednesday, April 11, 2001 3:38 PM
Subject: Re: 2 different networks under same domain


> sorry for not supplying all the information.
>
> i'm running version 8.2.3
>
> i've heard about views in bind9 and i am in the process of checking it
> out.  One thing i am confused about is whether i can allow certain
> programs to see certain views.  It sounds to me like views works based
> upon where you are within a network.
>
> Adam Lang wrote:
> >
> > What version of Bind are you running?
> >
> > Adam Lang
> > Systems Engineer
> > Rutgers Casualty Insurance Company
> > http://www.rutgersinsurance.com
> > ----- Original Message -----
> > From: "darcy w. christ" <darcy at elegant.com>
> > To: "bind" <bind-users at isc.org>
> > Sent: Wednesday, April 11, 2001 3:11 PM
> > Subject: 2 different networks under same domain
> >
> > >
> > > 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
>
> --
> ~darcy w. christ
> Elegant Communications Inc.
> 416.362.9772 x222 | 416.362.8324 fax