Yes I have thought of that. I ran into a few issues that I thought made the
solution cumbersome. Perhaps you solved these in a way that makes them

    1) Need to always use fully qualified names (only a problem when there are
    2) Need to bounce named a lot to avoid having records for networks that are
not currently connected to.
        (perhaps sufficient to edit search line in resolv.conf each time a
network gets added/deleted.)
    3) If the remote network consists of lots of subdomains the named config
becomes rather large.


Andrea Campi wrote:

> This is my only message in this thread, it's out of topic.
> On Thu, Nov 30, 2000 at 01:58:59PM -0600, Lars Fredriksen wrote:
> > Hi,
> >
> > I find myself connected to multiple networks and domains all the time,
> > and was wondering if anyone has solved (without using a chroot
> > environment) using a different resolv.conf for different shells?
> Have you thought about running your own non-authoritative DNS? If you use
> djbdns, this gives you the added benefit of being able to easily specify
> which DNS is authoritative for special, local domains. In general, having
> your local, caching-only (in bind parlance) DNS gives you better security
> and flexibility, and it's very easy to maintain. All of my machines, clients
> and servers, run like that, and I never had any problem.
> Bye,
>         Andrea
> --
>            Intel: where Quality is job number 0.9998782345!

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Reply via email to