On 07/02/2011 23:32, Andrew Pimlott wrote: > I have this problem too. I think there is a simple work-around. Just > move tun* down in /etc/resolvconf/interface-order. This will put the > VPN's nameservers at the end of /etc/resolv.conf, so your "normal" > nameserver will be used first. > > In fact, I think that's a better default for > /etc/resolvconf/interface-order, so I filed a wishlist bug: > http://bugs.debian.org/612351
It depends a lot on the local config of the VPN you are using. It can be a workaround for some user. It is a not fix for this bug (460200). In my university, it would be an error not to use the VPN provided DNS servers (they have entries for some resources on the VPN that are not visible to other external DNS). It seems more logical to me to ask VPN resolvers first and other next. And /etc/resolvconf/interface-order can be configured by the user to fit its needs if required. Regards, Vincent > Andrew -- Vincent Danjean Adresse: Laboratoire d'Informatique de Grenoble Téléphone: +33 4 76 61 20 11 ENSIMAG - antenne de Montbonnot Fax: +33 4 76 61 20 99 ZIRST 51, avenue Jean Kuntzmann Email: vincent.danj...@imag.fr 38330 Montbonnot Saint Martin -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org