On Thu, Apr 17, 2008 at 4:56 PM, John Clarke <[EMAIL PROTECTED]> wrote: > On Thu, Apr 17, 2008 at 09:05:33 +0545, Howard Lowndes wrote: > > Howard, > > > I don't want to start fiddling with dhclient, nor with /etc/resolv.conf, > > but I would like to get at least some of the internal zone presented to > > If you don't want to use resolvconf to sort it out (and I'm not > recommending you do, just noting it as an option), here are a > couple of solutions I've used with openvpn: > > If you only want localhost to be able to resolve the internal zone, > do a zone transfer from the remote name server after the vpn comes up > and populate /etc/hosts. When the vpn goes down (or the machine is > rebooted), remove the extra hostnames from /etc/hosts.
I was wondering about exactly that problem with my use of our company's vpn from my Ubuntu 7.10 laptop. I never got around to check this but we use an internal domain "company.local" for the internal IP address, wouldn't it be possible to configure a DNS server (bind9) on the laptop to forward .company.local to the internal DNS server and the rest to the 'default' DNS server? It looks like the "zone" statement with type "forward" would achieve just that. For Howards's original question, maybe he can just setup a forward zone for soho.lannet.com which forwards to the internal DNS server, and forwards the rest of the zones to the default upstream. (ref: http://www.bind9.net/manual/bind/9.3.2/Bv9ARM.ch06.html#zone_statement_grammar) If someone comes up with the exact incantation to do that I'd appreciate to see a copy of such a config. --Amos -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
