Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.os.linux.networking > #722
| From | Chris Davies <chris-usenet@roaima.co.uk> |
|---|---|
| Newsgroups | comp.os.linux.networking |
| Subject | Re: vpnc and resolv.conf |
| Date | 2011-10-25 15:50 +0100 |
| Organization | Roaima. Harrogate, North Yorkshire, UK |
| Message-ID | <jvuin8xjv7.ln2@news.roaima.co.uk> (permalink) |
| References | <1479b035-b3c2-43d7-98b7-0c9089d5a644@s14g2000vbj.googlegroups.com> <j8421l$5ov$1@dk3uz.ampr.org> <55a02bf0-f9f5-4308-9dd9-4f2679a2b599@v28g2000vby.googlegroups.com> |
blueparty <partner50449476@vansoftcorp.com> wrote:
> That parameter [DNSUpdate] does not exist in my version of vpnc. From
> Google I can see that it stopped working in older versions, while it was
> still present.
According to the README file included in the Debian distribution, this
parameter is indeed deprecated, but it was managed by the "vpnc-connect"
wrapper script anyway.
Taking a quick look through the new "vpnc-wrapper" script, it seems
to me that if you add this line as the second line of that script
(i.e. underneath the #!/bin/sh line), it will prevent updates to the
/etc/resolv.conf file:
INTERNAL_IP4_DNS=
Personally, I'd rather the maintainers had kept the DNSUpdate parameter.
Sigh.
Chris
Back to comp.os.linux.networking | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
vpnc and resolv.conf blueparty <partner50449476@vansoftcorp.com> - 2011-10-23 20:46 -0700
Re: vpnc and resolv.conf dk3uz@arrl.net (Edmund H. Ramm) - 2011-10-24 15:59 +0000
Re: vpnc and resolv.conf blueparty <partner50449476@vansoftcorp.com> - 2011-10-25 06:51 -0700
Re: vpnc and resolv.conf Chris Davies <chris-usenet@roaima.co.uk> - 2011-10-25 15:50 +0100
Re: vpnc and resolv.conf buck <buck@private.mil> - 2011-10-25 15:32 +0000
Re: vpnc and resolv.conf dk3uz@arrl.net (Edmund H. Ramm) - 2011-10-25 18:56 +0000
csiph-web