<?xml version="1.0" encoding="UTF-8"?>

<rss version="2.0" xmlns:blogChannel="http://backend.userland.com/blogChannelModule">

<channel>
<title>How do I prevent DNS leak through VPN? in Virtual Private Networking</title>
<link>http://www.dslreports.com/forum/r22274272</link>
<description></description>
<language>en</language>
<pubDate>Sun, 22 Nov 2009 21:22:12 EDT</pubDate>
<lastBuildDate>Sun, 22 Nov 2009 21:22:12 EDT</lastBuildDate>

<item>
<title>Re: How do I prevent DNS leak through VPN?</title>
<link>http://www.dslreports.com/forum/remark,22322974</link>
<description><![CDATA[<A HREF="/useremail/u/731304"><b>rjs1003</b></A> : DNS leaks... <br>I assume you're talking about where the dns requests go out to the local ISP even though other traffic gets sent via the tunnel (happens with typical MS-PPTP setups for example).<br>If you're using a VPN to prevent people seeing what you're browsing (eg if you're in a country where you don't want the government to see what you're accessing or you're using the VPN to access sites which the government blocks) then this kind of DNS leak allows a good idea of where you're browsing to... and also allows for a censor to change the address that is returned, leading your PC to who-knows-what-site.<br>Otherwise, leaking of local addresses is as stefaanE said, much less of an issue. Not information I like to get outside my firewall but not a disaster by itself (though of potential use to hackers trying to exploit any weaknesses your firewall does have)<br><br>Bob]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,22322974</guid>
<pubDate>Fri, 01 May 2009 08:22:02 EDT</pubDate>
</item>

<item>
<title>Re: How do I prevent DNS leak through VPN?</title>
<link>http://www.dslreports.com/forum/remark,22280456</link>
<description><![CDATA[<A HREF="/useremail/u/656330"><b>stefaanE</b></A> : DNS information is meant to be public, so leaking it cannot be a big security threat.<br><br>If you're talking about leaking internal DNS information, it hardly constitutes a threat, especially if you're using the customary private address ranges (10.x.x.x and friends). These ranges aren't routed on the Internet, and hence cannot be used as attack vectors.<br><br>The real security risk would be to use public addresses for internal systems, and not providing proper protection to these systems (especially if they are Windows based). In this case, leaking DNS information through a VPN is the least of your worries.<br><br>Take care,<br><br>Stefaan<br><small>--<br>"Technically, Windows is an 'operating system,' which means that it supplies your computer with the basic commands that it needs to suddenly, with no warning whatsoever, stop operating." -Dave Barry </small>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,22280456</guid>
<pubDate>Wed, 22 Apr 2009 17:53:50 EDT</pubDate>
</item>

<item>
<title>How do I prevent DNS leak through VPN?</title>
<link>http://www.dslreports.com/forum/remark,22274272</link>
<description><![CDATA[<A HREF="/useremail/u/0"><b>anon</b></A> : I'm using EAP-TTLS encryption VPN. The software is called SecureW2. I've found a guide on how to fix the DNS leak for OpenDNS, but how do I do it for SecureW2? Also, is leaking DNS a big security threat? (I'm assuming yes)<br><br>Here's the link for the OpenDNS guide that I've found.<br>&raquo;<A HREF="http://xerobank.com/support/articles/how-to-prevent-vpn-dns-leaks/" >xerobank.com/support/articles/ho&middot;&middot;&middot;s-leaks/</A>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,22274272</guid>
<pubDate>Tue, 21 Apr 2009 17:59:23 EDT</pubDate>
</item>

</channel>
</rss>
