On Tue, 25 Jun 2013 07:30:54 -0700 Aubrey Raech <aubreyra...@gmail.com> wrote:
> On Tue, 25 Jun 2013 16:09:02 +1200 > Joel Wirāmu Pauling <j...@aenertia.net> wrote: > > > Goes to syslog by default i.e /var/log/syslog IIRC. > > > > Your name resolution issue is seperate, and probably due to needing > > different name servers. Ensure you have a tun/tap device and IP etc > > from your vpn provider with ; > > > > $ip addr > > > > and > > > > $ip route show > > > > and pinging the (hopefully new) default gateway. > > > > Find out from your provider what dns servers you can use. Or at a > > pinch at opendns or googles global ones (8.8.8.8) into > > /etc/resolv.conf > > Changing my DNS to Google's in resolv.conf works!! It appears that my > ISP has me use a DNS server that is on the local network (aka, routed > through their modem), so of course it couldn't find it at the VPN > end! > > Now my problem is that resolv.conf resets my manual edits back to what > the automatic dhcp resolution sets it to, so I'll have to look into > how to make that persist. Thank you! > > I asked dpkg in #debian on Freenode, and was recommended the "override dns" entry, which says to modify my dhcp configuration in this way: # echo "supersede domain-name-servers 8.8.8.8, 8.8.4.4;" \ >> /etc/dhcp/dhclient.conf And now my problems appear to be solved. Thanks y'all! -- Aubrey "There are two types of people in the world: those who can extrapolate from incomplete data." -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130625080002.5a757a56@rosie
