Jump to content


Photo

"The remote name could not be resolved" [Win 10, workaround]

dns windows 10 connection

  • Please log in to reply
9 replies to this topic

#1 Tpk

Tpk

    Newbie

  • New Members
  • Pip
  • 4 posts

Posted 26 December 2016 - 09:54 PM

Like some others here, I too have an issue on Windows where after "Checking route", the vpn client throws out the error from the title and doesn't connect to a server. I've played around with different settings while reading logs trying to see what causes it and it seems that for some reason either Windows or the vpn client dislike when both your default (ISP) network connection and the TAP (VPN) network connection have the same DNS settings.

 

Fortunately, there's an easy workaround:

1) Make sure your default network connection's DNS are not one of AirVPN DNS servers (i.e. not 10.4.0.1). It can be either automatic or some of your other favorite DNS servers.

2) Check that the TAP network connection is set to automatic DNS servers (don't put any in manually).

3) In the 2.11 beta vpn client (I haven't tested on 2.10 stable) open Preferences (and click on "Reset to default settings" just in case) -> Advanced -> and then uncheck "Force all network interfaces for DNS". After that open the DNS settings tab just to make sure everything in there is set to default values (DNS Switch mode - Automatic, Check AirVPN DNS - yes, DNS Servers - blank).

 

That's it.

 

Now, there's one thing I'd like to mention. When doing all this I was worried that I would have a DNS leak because when I was using a different VPN service it would occasionally leak the DNS set in my default network connection's settings. However I've tested it out and there's no leak, and if you want to test it out for yourself I suggest using both ipleak and doileak, and for best results make sure you disconnect and reconnect several times to the same server and a few other servers in between tests, just to cover a wider ground.

 

Feel free to ask questions or leave comments.

 

P.S. As a general tip - I recommend you don't use your ISP's DNS settings for your default connection (unless you have to) cause there are some great uncensored and faster DNS servers out there. And as for the VPN DNS server I recommend you do stick with default AirVPN DNS servers cause it's useful having your IP and DNS address be the same.



#2 LZ1

LZ1

    It's nice to be nice to nice people

  • Moderators
  • 1840 posts

Posted 27 December 2016 - 10:44 AM

Hello!

 

Very nice I must say. This should be stickied lol ^__^.

 

Thank you for sharing with us and welcome to AirVPN!


Hi there, are you new to AirVPN? Many of your questions are already answered in this guide. Its Guides Section has guides on Linux/Torrenting/Blocked sites & many other topics too.
Moderators do not speak on behalf of AirVPN. Only the Official Staff account does. Please read the First Questions section in the link above for more details, thank you.
Did you make a guide or how-to for something? Then contact me to get it listed in my new user guide's Guides Section, so that the community can find it more easily.

Tired of Windows? Why Linux Is Better.

#3 Staff

Staff

    Advanced Member

  • Staff
  • PipPipPip
  • 7568 posts

Posted 27 December 2016 - 01:57 PM

Hello!

 

About option "Force all network interfaces for DNS": some people have DNS leak if unchecked, it's still under investigation.

With
- DNS -> DNS Switch mode - Automatic
- DNS -> Check AirVPN DNS - YES
- Advanced -> Ensure DNS Lock - YES
- Advanced -> Force all network interfaces for DNS - YES

1) do you have ALWAYS a "The remote name could not be resolved" error, or only sometimes?
2) if you uncheck "Force all network interfaces for DNS" as explained in your topic/post, do you have ALWAYS a successful connection?
In this case, after an established, successful connection, please post the log generated by "life belt" icon.

 

It's important for us to understand if your issue is always reproducible. Thank you.

 

Kind regards



#4 MikeFromIT

MikeFromIT

    Newbie

  • Members
  • Pip
  • 9 posts

Posted 27 December 2016 - 05:07 PM

I tried this and am still having issues.Get's hung on checking route and then the usual hostname could not be resolved.



#5 LZ1

LZ1

    It's nice to be nice to nice people

  • Moderators
  • 1840 posts

Posted 27 December 2016 - 06:08 PM

I tried this and am still having issues.Get's hung on checking route and then the usual hostname could not be resolved.

Please post your logs then :).

 

Have you tried the usual responses to the checking route problem?


Hi there, are you new to AirVPN? Many of your questions are already answered in this guide. Its Guides Section has guides on Linux/Torrenting/Blocked sites & many other topics too.
Moderators do not speak on behalf of AirVPN. Only the Official Staff account does. Please read the First Questions section in the link above for more details, thank you.
Did you make a guide or how-to for something? Then contact me to get it listed in my new user guide's Guides Section, so that the community can find it more easily.

Tired of Windows? Why Linux Is Better.

#6 Tpk

Tpk

    Newbie

  • New Members
  • Pip
  • 4 posts

Posted 27 December 2016 - 09:59 PM

Hello!

 

About option "Force all network interfaces for DNS": some people have DNS leak if unchecked, it's still under investigation.

With
- DNS -> DNS Switch mode - Automatic
- DNS -> Check AirVPN DNS - YES
- Advanced -> Ensure DNS Lock - YES
- Advanced -> Force all network interfaces for DNS - YES

1) do you have ALWAYS a "The remote name could not be resolved" error, or only sometimes?
2) if you uncheck "Force all network interfaces for DNS" as explained in your topic/post, do you have ALWAYS a successful connection?
In this case, after an established, successful connection, please post the log generated by "life belt" icon.

 

It's important for us to understand if your issue is always reproducible. Thank you.

 

Kind regards

 

1) Yes, always. Here's a log:

 

Spoiler
 
2) No, not always. As I said in my first post, the entire issue seems to be with the fact that either Windows or Eddie don't like when both ISP and VPN DNS servers are set to the same one. Here's a log of what happens when I turn off "Force all network interfaces for DNS" and manually set ISP DNS to 10.4.0.1 :
 
Spoiler

 

And here's a log what happens when I turn off both "Force all network interfaces for DNS" and change "DNS Switch mode" to disabled, but at the same time manually input 8.8.8.8 as the DNS server for both ISP and TAP network connections:

 

Spoiler
 
I even tried one more time with disabling "Check AirVPN DNS" in this case but the results were the same.
 
3) Here's a log from a successful connection that was achieved using methods described in my first post (all Eddie settings default other than "Force all network interfaces for DNS" turned off; ISP DNS automatic (or manual but NOT 10.4.0.1 i.e. not the same as TAP DNS is going to be) :
 
Spoiler
 
P.S. I just realized someone gave me 3 months of VPN for free, thanks for that! 


#7 LZ1

LZ1

    It's nice to be nice to nice people

  • Moderators
  • 1840 posts

Posted 27 December 2016 - 10:02 PM

Sweet feedback. You deserve it and Air must think you do so too, given they rewarded you. If you go to invoices and then the "paid" tab, you'll be able to see. Brilliant use of spoilers by the way, you deserve a medal for that alone! :lol: ^_^


Hi there, are you new to AirVPN? Many of your questions are already answered in this guide. Its Guides Section has guides on Linux/Torrenting/Blocked sites & many other topics too.
Moderators do not speak on behalf of AirVPN. Only the Official Staff account does. Please read the First Questions section in the link above for more details, thank you.
Did you make a guide or how-to for something? Then contact me to get it listed in my new user guide's Guides Section, so that the community can find it more easily.

Tired of Windows? Why Linux Is Better.

#8 Tpk

Tpk

    Newbie

  • New Members
  • Pip
  • 4 posts

Posted 27 December 2016 - 10:14 PM

Sweet feedback. You deserve it and Air must think you do so too, given they rewarded you. If you go to invoices and then the "paid" tab, you'll be able to see. Brilliant use of spoilers by the way, you deserve a medal for that alone! :lol: ^_^

 

Thanks, it says "Free - 3 months" last night at 1am, sweet! Btw your link leads to .info instead of .org  :|



#9 LZ1

LZ1

    It's nice to be nice to nice people

  • Moderators
  • 1840 posts

Posted 27 December 2016 - 10:23 PM

Oh, well you seem to have found it anyhow haha :). Good effort.


Hi there, are you new to AirVPN? Many of your questions are already answered in this guide. Its Guides Section has guides on Linux/Torrenting/Blocked sites & many other topics too.
Moderators do not speak on behalf of AirVPN. Only the Official Staff account does. Please read the First Questions section in the link above for more details, thank you.
Did you make a guide or how-to for something? Then contact me to get it listed in my new user guide's Guides Section, so that the community can find it more easily.

Tired of Windows? Why Linux Is Better.

#10 MikeFromIT

MikeFromIT

    Newbie

  • Members
  • Pip
  • 9 posts

Posted 29 December 2016 - 06:10 PM

I tried this and am still having issues.Get's hung on checking route and then the usual hostname could not be resolved.

Please post your logs then :).

 

Have you tried the usual responses to the checking route problem?

 

Here's a copy of my logs from today while attempting to connect. It doesn't look like there's any errors to me, it just hangs at Checking Route and then times out.

 

I 2016.12.29 12:02:49 - Eddie client version: 2.11.9 / windows_x64, System: Windows, Name: Microsoft Windows NT 10.0.14393.0, Mono/.Net Framework: v4.0.30319
. 2016.12.29 12:02:49 - Reading options from C:\Users\Michael\AppData\Local\AirVPN\AirVPN.xml
. 2016.12.29 12:02:50 - Data path: C:\Users\Michael\AppData\Local\AirVPN
. 2016.12.29 12:02:50 - Application path: C:\Program Files\AirVPN
. 2016.12.29 12:02:50 - Executable path: C:\Program Files\AirVPN\AirVPN.exe
. 2016.12.29 12:02:50 - Command line arguments (1): path="home"
. 2016.12.29 12:02:50 - Operating System: Microsoft Windows NT 10.0.14393.0
I 2016.12.29 12:02:51 - OpenVPN Driver - TAP-Windows Adapter V9, version 9.21.2
I 2016.12.29 12:02:51 - OpenVPN - Version: 2.3.13 - OpenSSL 1.0.2j  26 Sep 2016, LZO 2.09 (C:\Program Files\AirVPN\openvpn.exe)
I 2016.12.29 12:02:51 - SSH - Version: plink 0.67 (C:\Program Files\AirVPN\plink.exe)
I 2016.12.29 12:02:51 - SSL - Version: stunnel 5.37 (C:\Program Files\AirVPN\stunnel.exe)
! 2016.12.29 12:02:52 - Ready
. 2016.12.29 12:02:52 - Updating systems & servers data ...
. 2016.12.29 12:02:53 - Systems & servers data update completed
I 2016.12.29 12:02:58 - Session starting.
. 2016.12.29 12:03:07 - IPv6 disabled with packet filtering.
I 2016.12.29 12:03:07 - Checking authorization ...
I 2016.12.29 12:03:08 - Cancel requested.
. 2016.12.29 12:03:08 - IPv6 restored with packet filtering.
! 2016.12.29 12:03:16 - Session terminated.
I 2016.12.29 12:03:20 - Session starting.
. 2016.12.29 12:03:23 - Shell of 'cmd.exe','/c net stop dnscache' done sync in 2766 ms
. 2016.12.29 12:03:24 - Shell of 'cmd.exe','/c net start dnscache' done sync in 187 ms
. 2016.12.29 12:03:24 - Shell of 'cmd.exe','/c ipconfig /flushdns' done sync in 125 ms
. 2016.12.29 12:03:27 - Shell of 'cmd.exe','/c ipconfig /registerdns' done sync in 3125 ms
. 2016.12.29 12:03:27 - IPv6 disabled with packet filtering.
I 2016.12.29 12:03:27 - Checking authorization ...
! 2016.12.29 12:03:27 - Connecting to Tejat (Canada, Toronto, Ontario)
. 2016.12.29 12:03:28 - OpenVPN > OpenVPN 2.3.13 x86_64-w64-mingw32 [SSL (OpenSSL)] [LZO] [IPv6] built on Nov 10 2016
. 2016.12.29 12:03:28 - OpenVPN > Windows version 6.2 (Windows 8 or greater) 64bit
. 2016.12.29 12:03:28 - OpenVPN > library versions: OpenSSL 1.0.2j  26 Sep 2016, LZO 2.09
. 2016.12.29 12:03:28 - OpenVPN > MANAGEMENT: TCP Socket listening on [AF_INET]127.0.0.1:3100
. 2016.12.29 12:03:28 - OpenVPN > Control Channel Authentication: tls-auth using INLINE static key file
. 2016.12.29 12:03:28 - OpenVPN > Outgoing Control Channel Authentication: Using 160 bit message hash 'SHA1' for HMAC authentication
. 2016.12.29 12:03:28 - OpenVPN > Incoming Control Channel Authentication: Using 160 bit message hash 'SHA1' for HMAC authentication
. 2016.12.29 12:03:28 - OpenVPN > Socket Buffers: R=[65536->262144] S=[65536->262144]
. 2016.12.29 12:03:28 - OpenVPN > UDPv4 link local: [undef]
. 2016.12.29 12:03:28 - OpenVPN > UDPv4 link remote: [AF_INET]184.75.221.194:443
. 2016.12.29 12:03:28 - OpenVPN > TLS: Initial packet from [AF_INET]184.75.221.194:443, sid=d12fffd8 df3a8d7b
. 2016.12.29 12:03:30 - OpenVPN > VERIFY OK: depth=1, C=IT, ST=IT, L=Perugia, O=airvpn.org, CN=airvpn.org CA, emailAddress=info@airvpn.org
. 2016.12.29 12:03:30 - OpenVPN > Validating certificate key usage
. 2016.12.29 12:03:30 - OpenVPN > ++ Certificate has key usage  00a0, expects 00a0
. 2016.12.29 12:03:31 - OpenVPN > VERIFY KU OK
. 2016.12.29 12:03:31 - OpenVPN > Validating certificate extended key usage
. 2016.12.29 12:03:31 - OpenVPN > ++ Certificate has EKU (str) TLS Web Server Authentication, expects TLS Web Server Authentication
. 2016.12.29 12:03:31 - OpenVPN > VERIFY EKU OK
. 2016.12.29 12:03:31 - OpenVPN > VERIFY OK: depth=0, C=IT, ST=IT, L=Perugia, O=airvpn.org, CN=server, emailAddress=info@airvpn.org
. 2016.12.29 12:03:31 - OpenVPN > Data Channel Encrypt: Cipher 'AES-256-CBC' initialized with 256 bit key
. 2016.12.29 12:03:31 - OpenVPN > Data Channel Encrypt: Using 160 bit message hash 'SHA1' for HMAC authentication
. 2016.12.29 12:03:31 - OpenVPN > Data Channel Decrypt: Cipher 'AES-256-CBC' initialized with 256 bit key
. 2016.12.29 12:03:31 - OpenVPN > Data Channel Decrypt: Using 160 bit message hash 'SHA1' for HMAC authentication
. 2016.12.29 12:03:31 - OpenVPN > Control Channel: TLSv1.2, cipher TLSv1/SSLv3 DHE-RSA-AES256-GCM-SHA384, 4096 bit RSA
. 2016.12.29 12:03:31 - OpenVPN > [server] Peer Connection Initiated with [AF_INET]184.75.221.194:443
. 2016.12.29 12:03:33 - OpenVPN > SENT CONTROL [server]: 'PUSH_REQUEST' (status=1)
. 2016.12.29 12:03:33 - OpenVPN > PUSH: Received control message: 'PUSH_REPLY,redirect-gateway def1 bypass-dhcp,dhcp-option DNS 10.4.0.1,comp-lzo no,route-gateway 10.4.0.1,topology subnet,ping 10,ping-restart 60,ifconfig 10.4.14.146 255.255.0.0'
. 2016.12.29 12:03:33 - OpenVPN > OPTIONS IMPORT: timers and/or timeouts modified
. 2016.12.29 12:03:33 - OpenVPN > OPTIONS IMPORT: LZO parms modified
. 2016.12.29 12:03:33 - OpenVPN > OPTIONS IMPORT: --ifconfig/up options modified
. 2016.12.29 12:03:33 - OpenVPN > OPTIONS IMPORT: route options modified
. 2016.12.29 12:03:33 - OpenVPN > OPTIONS IMPORT: route-related options modified
. 2016.12.29 12:03:33 - OpenVPN > OPTIONS IMPORT: --ip-win32 and/or --dhcp-option options modified
. 2016.12.29 12:03:33 - OpenVPN > ROUTE_GATEWAY 192.168.1.254/255.255.255.0 I=11 HWADDR=d0:57:7b:f7:c8:49
. 2016.12.29 12:03:33 - OpenVPN > do_ifconfig, tt->ipv6=0, tt->did_ifconfig_ipv6_setup=0
. 2016.12.29 12:03:33 - OpenVPN > open_tun, tt->ipv6=0
. 2016.12.29 12:03:34 - OpenVPN > TAP-WIN32 device [Ethernet] opened: \\.\Global\{8BB804BB-2245-421B-9CB8-F7135C8FB1E0}.tap
. 2016.12.29 12:03:34 - OpenVPN > TAP-Windows Driver Version 9.21
. 2016.12.29 12:03:34 - OpenVPN > Set TAP-Windows TUN subnet mode network/local/netmask = 10.4.0.0/10.4.14.146/255.255.0.0 [SUCCEEDED]
. 2016.12.29 12:03:34 - OpenVPN > Notified TAP-Windows driver to set a DHCP IP/netmask of 10.4.14.146/255.255.0.0 on interface {8BB804BB-2245-421B-9CB8-F7135C8FB1E0} [DHCP-serv: 10.4.255.254, lease-time: 31536000]
. 2016.12.29 12:03:34 - OpenVPN > Successful ARP Flush on interface [9] {8BB804BB-2245-421B-9CB8-F7135C8FB1E0}
. 2016.12.29 12:03:38 - OpenVPN > TEST ROUTES: 1/1 succeeded len=0 ret=1 a=0 u/d=up
. 2016.12.29 12:03:38 - OpenVPN > C:\windows\system32\route.exe ADD 184.75.221.194 MASK 255.255.255.255 192.168.1.254
. 2016.12.29 12:03:38 - OpenVPN > ROUTE: CreateIpForwardEntry succeeded with dwForwardMetric1=55 and dwForwardType=4
. 2016.12.29 12:03:38 - OpenVPN > Route addition via IPAPI succeeded [adaptive]
. 2016.12.29 12:03:38 - OpenVPN > C:\windows\system32\route.exe ADD 0.0.0.0 MASK 128.0.0.0 10.4.0.1
. 2016.12.29 12:03:38 - OpenVPN > ROUTE: CreateIpForwardEntry succeeded with dwForwardMetric1=35 and dwForwardType=4
. 2016.12.29 12:03:38 - OpenVPN > Route addition via IPAPI succeeded [adaptive]
. 2016.12.29 12:03:38 - OpenVPN > C:\windows\system32\route.exe ADD 128.0.0.0 MASK 128.0.0.0 10.4.0.1
. 2016.12.29 12:03:38 - OpenVPN > ROUTE: CreateIpForwardEntry succeeded with dwForwardMetric1=35 and dwForwardType=4
. 2016.12.29 12:03:38 - OpenVPN > Route addition via IPAPI succeeded [adaptive]
. 2016.12.29 12:03:38 - Starting Management Interface
. 2016.12.29 12:03:38 - OpenVPN > Initialization Sequence Completed
. 2016.12.29 12:03:38 - DNS leak protection with packet filtering enabled.
. 2016.12.29 12:03:38 - DNS of a network adapter forced (TAP-Windows Adapter V9, from automatic (10.4.0.1) to 10.4.0.1)
I 2016.12.29 12:03:39 - Flushing DNS
. 2016.12.29 12:03:44 - Shell of 'cmd.exe','/c net stop dnscache' done sync in 5282 ms
. 2016.12.29 12:03:44 - Shell of 'cmd.exe','/c net start dnscache' done sync in 156 ms
. 2016.12.29 12:03:44 - Shell of 'cmd.exe','/c ipconfig /flushdns' done sync in 109 ms
. 2016.12.29 12:03:47 - Shell of 'cmd.exe','/c ipconfig /registerdns' done sync in 3125 ms
I 2016.12.29 12:03:47 - Checking route
W 2016.12.29 12:04:48 - The operation has timed out
! 2016.12.29 12:04:48 - Disconnecting
. 2016.12.29 12:04:48 - Management - Send 'signal SIGTERM'
. 2016.12.29 12:04:48 - OpenVPN > MANAGEMENT: CMD 'signal SIGTERM'
. 2016.12.29 12:04:48 - OpenVpn Management > >INFO:OpenVPN Management Interface Version 1 -- type 'help' for more info
. 2016.12.29 12:04:48 - OpenVPN > SIGTERM received, sending exit notification to peer
. 2016.12.29 12:04:53 - OpenVPN > C:\windows\system32\route.exe DELETE 184.75.221.194 MASK 255.255.255.255 192.168.1.254
. 2016.12.29 12:04:53 - OpenVPN > Route deletion via IPAPI succeeded [adaptive]
. 2016.12.29 12:04:53 - OpenVPN > C:\windows\system32\route.exe DELETE 0.0.0.0 MASK 128.0.0.0 10.4.0.1
. 2016.12.29 12:04:53 - OpenVPN > Route deletion via IPAPI succeeded [adaptive]
. 2016.12.29 12:04:53 - OpenVPN > C:\windows\system32\route.exe DELETE 128.0.0.0 MASK 128.0.0.0 10.4.0.1
. 2016.12.29 12:04:53 - OpenVPN > Route deletion via IPAPI succeeded [adaptive]
. 2016.12.29 12:04:53 - OpenVPN > Closing TUN/TAP interface
. 2016.12.29 12:04:54 - OpenVPN > SIGTERM[soft,exit-with-notification] received, process exiting
. 2016.12.29 12:04:54 - Connection terminated.
. 2016.12.29 12:04:54 - DNS of a network adapter restored to original settings (TAP-Windows Adapter V9, to automatic)
. 2016.12.29 12:04:54 - DNS leak protection with packet filtering disabled.
I 2016.12.29 12:04:57 - Checking authorization ...
! 2016.12.29 12:04:58 - Connecting to Sadalbari (Canada, Toronto, Ontario)
. 2016.12.29 12:04:58 - OpenVPN > OpenVPN 2.3.13 x86_64-w64-mingw32 [SSL (OpenSSL)] [LZO] [IPv6] built on Nov 10 2016
. 2016.12.29 12:04:58 - OpenVPN > Windows version 6.2 (Windows 8 or greater) 64bit
. 2016.12.29 12:04:58 - OpenVPN > library versions: OpenSSL 1.0.2j  26 Sep 2016, LZO 2.09
. 2016.12.29 12:04:58 - OpenVPN > MANAGEMENT: TCP Socket listening on [AF_INET]127.0.0.1:3100
. 2016.12.29 12:04:58 - OpenVPN > Control Channel Authentication: tls-auth using INLINE static key file
. 2016.12.29 12:04:58 - OpenVPN > Outgoing Control Channel Authentication: Using 160 bit message hash 'SHA1' for HMAC authentication
. 2016.12.29 12:04:58 - OpenVPN > Incoming Control Channel Authentication: Using 160 bit message hash 'SHA1' for HMAC authentication
. 2016.12.29 12:04:58 - OpenVPN > Socket Buffers: R=[65536->262144] S=[65536->262144]
. 2016.12.29 12:04:58 - OpenVPN > UDPv4 link local: [undef]
. 2016.12.29 12:04:58 - OpenVPN > UDPv4 link remote: [AF_INET]184.75.221.178:443
. 2016.12.29 12:04:58 - OpenVPN > TLS: Initial packet from [AF_INET]184.75.221.178:443, sid=ff04f78a f490788d
. 2016.12.29 12:05:01 - OpenVPN > VERIFY OK: depth=1, C=IT, ST=IT, L=Perugia, O=airvpn.org, CN=airvpn.org CA, emailAddress=info@airvpn.org
. 2016.12.29 12:05:01 - OpenVPN > Validating certificate key usage
. 2016.12.29 12:05:01 - OpenVPN > ++ Certificate has key usage  00a0, expects 00a0
. 2016.12.29 12:05:01 - OpenVPN > VERIFY KU OK
. 2016.12.29 12:05:01 - OpenVPN > Validating certificate extended key usage
. 2016.12.29 12:05:01 - OpenVPN > ++ Certificate has EKU (str) TLS Web Server Authentication, expects TLS Web Server Authentication
. 2016.12.29 12:05:01 - OpenVPN > VERIFY EKU OK
. 2016.12.29 12:05:01 - OpenVPN > VERIFY OK: depth=0, C=IT, ST=IT, L=Perugia, O=airvpn.org, CN=server, emailAddress=info@airvpn.org






Similar Topics Collapse


1 user(s) are reading this topic

0 members, 1 guests, 0 anonymous users

Servers online. Online Sessions: 15090 - BW: 51316 Mbit/sYour IP: 54.162.133.222Guest Access.