ANSWERED OpenDNS & AirVPN

[psikey 1]

I use OpenDNS to restrict various access on my home network (protect the kids) but on my server I use the AirVPN client (have OpenDNS DNS addresses in router)

 

This used to effectively bypass OpenDNS allowing access to all sites but for some reason its started to work on  my regular AirVPN servers I connect to.

 

In the OpenDNS pages there is a config page for adding VPN domains and have added 31-193-12-75.static.hostnoc.net but still be blocked ??

 

What am I misunderstanding to get this working again? 

 

If I IP-lookup in web browser I am shown as on one of AirVPN servers as does my uTorrent test using CheckMyTorrentIp.

 

I'm on Windows 8 Pro

 

Also I use Plex and Remote Desktop connection to the server. Should I still be able to connect to my server remotely when I have AirVPN running because I can even though I'm pointing to my Domain Name (dyndns name).  Am I actually being protected by AirVPN ??

 

When I change AirVPN client the uTorrent log does seem to change:

 

[2013-05-14 12:40:49]  Changing IP address from 10.4.1.38 to 192.168.1.100
[2013-05-14 12:41:15]  Changing IP address from 192.168.1.100 to 10.4.38.234
[2013-05-14 12:41:55]  Changing IP address from 10.4.38.234 to 192.168.1.100
[2013-05-14 12:42:28]  Changing IP address from 192.168.1.100 to 10.4.15.158
 

 

 

 

Thanks

 

 

 

OPENDNS setting page

 

Exceptions for VPN users

VPN users should add the domain they VPN into as an exception. This will make sure your VPN connection is unaffected by OpenDNS.
Example: vpn.mycompany.com

  Add to all personal networks

Your exceptions

Note: some of these may have been added automatically by the OpenDNS Updater software.

31-193-12-75.static.hostnoc.net

[psikey 1]

No help / advice on these questions 

[Staff 10118]

Hello!

 

While you're connected to an Air VPN server with Windows 8 set the OpenDNS servers IP addresses as primary as secondary DNS in your TAP-Win32 interface (if you wish to tunnel DNS queries to OpenDNS):

208.67.222.222

208.67.220.220

 

Remember that not using Air DNS servers will prevent the system to use our anti-censorship features and our anti geo-blocking features.

 

If OpenDNS should block any of our domain names (but we are not aware of that) you can anyway connect to the VPN servers through their IP addresses.

 

Kind regards

[psikey 1]

OK the TAP-Windows Adapter V9 that becomes active when AirVPN launches for bootis shows a DNS of 10.0.4.1 which is the DNS for this server but my Ethernet connection on the server is set to automatic so looks like its using the OpenDNS  settings entered in the router.

 

If I set the Server Ethernet connection to fixed DNS of 10.0.4.1 Primary than say 8.8.8.8 secondary I can get it to work. Need the 2nd DNS otherwise AirVPN isn't found by the Client.

 

I've made no changes in the router which is still set to the two OpenDNS addresses.

 

Is this setup correct way of doing it (Have checked for leaks and all OK ref: https://airvpn.org/topic/9289-dns-leaks-and-how-to-fix-them/)

 

Even though the DNS was still being directed to the OpenDNS servers for web searches, can I still be sure that the uTorrent client and IP Lookup checks still showed me externally as being on AirVPN?

[Staff 10118]

  On 5/17/2013 at 10:17 AM, psikey said:

OK the TAP-Windows Adapter V9 that becomes active when AirVPN launches for bootis shows a DNS of 10.0.4.1 which is the DNS for this server but my Ethernet connection on the server is set to automatic so looks like its using the OpenDNS  settings entered in the router.

Hello!

 

Correct. We'll post a more elaborate explanation about Windows DNS leaks.

 

  Quote

If I set the Server Ethernet connection to fixed DNS of 10.0.4.1 Primary than say 8.8.8.8 secondary I can get it to work. Need the 2nd DNS otherwise AirVPN isn't found by the Client.

The client needs to resolve airvpn.org to show you the list of servers and more. You can put 10.5.0.1 as secondary DNS of your physical network card(s) in order to prevent DNS leaks, then have airvpn.org resolved through the hosts. Edit the hosts file, add the lines:

85.17.207.151 airvpn.org

212.117.180.25 airvpn.org

 

Side note: due to Windows limitations, should you need to use OpenDNS IN the tunnel, or in general to send out encrypted DNS queries inside the tunnel to some DNS of your choice, you will need to force OpenDNS IP addresses (or your favorite DNS IP addresses) in the TUN/TAP network adapter.

 

Kind regards

[Baraka 32]

FYI, 85.17.207.151 is broken right now. 212.117.180.25 isn't. This site was unaccessible to me for the better part of the past 12 hours because of this issue. I found out the problem when I started playing with my hosts file. I had no entry for either IP before. If I don't add anything to hosts, it defaults to the unresponsive 85.17.207.151 address. Strangely enough, when disconnected from the VPN I am able to properly resolve and reach airvpn.org without any entries in my hosts file. The only way I can reach this site when connected is with the 212.117.180.25 airvpn.org entry in hosts.

 

Please fix this problem ASAP, since I think it's serious if you can't come here to check your settings.

 

  On 5/17/2013 at 2:26 PM, Staff said:

 

  On 5/17/2013 at 10:17 AM, psikey said:

OK the TAP-Windows Adapter V9 that becomes active when AirVPN launches for bootis shows a DNS of 10.0.4.1 which is the DNS for this server but my Ethernet connection on the server is set to automatic so looks like its using the OpenDNS  settings entered in the router.

Hello!

Correct. We'll post a more elaborate explanation about Windows DNS leaks.
 

  Quote

>If I set the Server Ethernet connection to fixed DNS of 10.0.4.1 Primary than say 8.8.8.8 secondary I can get it to work. Need the 2nd DNS otherwise AirVPN isn't found by the Client.

The client needs to resolve airvpn.org to show you the list of servers and more. You can put 10.5.0.1 as secondary DNS of your physical network card(s) in order to prevent DNS leaks, then have airvpn.org resolved through the hosts. Edit the hosts file, add the lines:
85.17.207.151 airvpn.org
212.117.180.25 airvpn.org

Side note: due to Windows limitations, should you need to use OpenDNS IN the tunnel, or in general to send out encrypted DNS queries inside the tunnel to some DNS of your choice, you will need to force OpenDNS IP addresses (or your favorite DNS IP addresses) in the TUN/TAP network adapter.

Kind regards

 

[Staff 10118]

@Baraka

 

There are no problems with 85.17.207.151. From which VPN server you're unable to access it?

 

Kind regards

[Baraka 32]

It was definitely not working earlier. But it's working now. I made no changes to my configuration except for the addition of those two lines to hosts.

 

I'm happy it's working now. Thanks for responding.