Jump to content


Photo

Checking DNS failed

Linux Eddie

  • Please log in to reply
2 replies to this topic

#1 Tman1677

Tman1677

    Newbie

  • New Members
  • Pip
  • 1 posts

Posted 11 March 2018 - 01:55 AM

I've seen many posts on this where they say the solution is to go into settings and turn off dns checks, but as I'm running Eddie from a CLI I can't find a settings file to change. 

I 2018.03.10 20:52:38 - Session starting.
I 2018.03.10 20:52:38 - Checking authorization ...
! 2018.03.10 20:52:39 - Connecting to Almach (Canada, Toronto, Ontario)
. 2018.03.10 20:52:39 - OpenVPN > OpenVPN 2.4.3 x86_64-unknown-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [MH/PKTINFO] [AEAD] built on Aug  9 2017
. 2018.03.10 20:52:39 - OpenVPN > library versions: OpenSSL 1.0.2l  25 May 2017, LZO 2.10
. 2018.03.10 20:52:39 - Connection to OpenVPN Management Interface
. 2018.03.10 20:52:39 - OpenVPN > MANAGEMENT: TCP Socket listening on [AF_INET]127.0.0.1:3100
. 2018.03.10 20:52:39 - OpenVPN > Outgoing Control Channel Authentication: Using 160 bit message hash 'SHA1' for HMAC authentication
. 2018.03.10 20:52:39 - OpenVPN > Incoming Control Channel Authentication: Using 160 bit message hash 'SHA1' for HMAC authentication
. 2018.03.10 20:52:39 - OpenVPN > TCP/UDP: Preserving recently used remote address: [AF_INET]199.19.94.12:443
. 2018.03.10 20:52:39 - OpenVPN > Socket Buffers: R=[212992->212992] S=[212992->212992]
. 2018.03.10 20:52:39 - OpenVPN > UDP link local: (not bound)
. 2018.03.10 20:52:39 - OpenVPN > UDP link remote: [AF_INET]199.19.94.12:443
. 2018.03.10 20:52:39 - OpenVPN > TLS: Initial packet from [AF_INET]199.19.94.12:443, sid=3958ac30 e5b2bfd4
. 2018.03.10 20:52:39 - OpenVPN > VERIFY OK: depth=1, C=IT, ST=IT, L=Perugia, O=airvpn.org, CN=airvpn.org CA, emailAddress=info@airvpn.org
. 2018.03.10 20:52:39 - OpenVPN > VERIFY KU OK
. 2018.03.10 20:52:39 - OpenVPN > Validating certificate extended key usage
. 2018.03.10 20:52:39 - OpenVPN > ++ Certificate has EKU (str) TLS Web Server Authentication, expects TLS Web Server Authentication
. 2018.03.10 20:52:39 - OpenVPN > VERIFY EKU OK
. 2018.03.10 20:52:39 - OpenVPN > VERIFY OK: depth=0, C=IT, ST=IT, L=Perugia, O=airvpn.org, CN=Almach, emailAddress=info@airvpn.org
. 2018.03.10 20:52:39 - OpenVPN > MANAGEMENT: Client connected from [AF_INET]127.0.0.1:3100
. 2018.03.10 20:52:39 - OpenVPN > Control Channel: TLSv1.2, cipher TLSv1/SSLv3 ECDHE-RSA-AES256-GCM-SHA384, 4096 bit RSA
. 2018.03.10 20:52:39 - OpenVPN > [Almach] Peer Connection Initiated with [AF_INET]199.19.94.12:443
. 2018.03.10 20:52:40 - OpenVPN > SENT CONTROL [Almach]: 'PUSH_REQUEST' (status=1)
. 2018.03.10 20:52:40 - OpenVPN > PUSH: Received control message: 'PUSH_REPLY,comp-lzo no,redirect-gateway def1 bypass-dhcp,dhcp-option DNS 10.4.0.1,route-gateway 10.4.0.1,topology subnet,ping 10,ping-restart 60,ifconfig 10.4.24.80 255.255.0.0,peer-id 49,cipher AES-256-GCM'
. 2018.03.10 20:52:40 - OpenVPN > OPTIONS IMPORT: timers and/or timeouts modified
. 2018.03.10 20:52:40 - OpenVPN > OPTIONS IMPORT: compression parms modified
. 2018.03.10 20:52:40 - OpenVPN > OPTIONS IMPORT: --ifconfig/up options modified
. 2018.03.10 20:52:40 - OpenVPN > OPTIONS IMPORT: route options modified
. 2018.03.10 20:52:40 - OpenVPN > OPTIONS IMPORT: route-related options modified
. 2018.03.10 20:52:40 - OpenVPN > OPTIONS IMPORT: --ip-win32 and/or --dhcp-option options modified
. 2018.03.10 20:52:40 - OpenVPN > OPTIONS IMPORT: peer-id set
. 2018.03.10 20:52:40 - OpenVPN > OPTIONS IMPORT: adjusting link_mtu to 1625
. 2018.03.10 20:52:40 - OpenVPN > OPTIONS IMPORT: data channel crypto options modified
. 2018.03.10 20:52:40 - OpenVPN > Data Channel: using negotiated cipher 'AES-256-GCM'
. 2018.03.10 20:52:40 - OpenVPN > Data Channel Encrypt: Cipher 'AES-256-GCM' initialized with 256 bit key
. 2018.03.10 20:52:40 - OpenVPN > Data Channel Decrypt: Cipher 'AES-256-GCM' initialized with 256 bit key
. 2018.03.10 20:52:40 - OpenVPN > ROUTE_GATEWAY 192.168.86.1/255.255.255.0 IFACE=ens33 HWADDR=90:fb:a6:02:98:45
. 2018.03.10 20:52:40 - OpenVPN > TUN/TAP device tun0 opened
. 2018.03.10 20:52:40 - OpenVPN > TUN/TAP TX queue length set to 100
. 2018.03.10 20:52:40 - OpenVPN > do_ifconfig, tt->did_ifconfig_ipv6_setup=0
. 2018.03.10 20:52:40 - OpenVPN > /sbin/ip link set dev tun0 up mtu 1500
. 2018.03.10 20:52:40 - OpenVPN > /sbin/ip addr add dev tun0 10.4.24.80/16 broadcast 10.4.255.255
. 2018.03.10 20:52:45 - OpenVPN > /sbin/ip route add 199.19.94.12/32 via 192.168.86.1
. 2018.03.10 20:52:45 - OpenVPN > /sbin/ip route add 0.0.0.0/1 via 10.4.0.1
. 2018.03.10 20:52:45 - OpenVPN > /sbin/ip route add 128.0.0.0/1 via 10.4.0.1
. 2018.03.10 20:52:45 - /etc/resolv.conf moved to /etc/resolv.conf.eddie as backup
. 2018.03.10 20:52:45 - DNS of the system updated to VPN DNS (Rename method: /etc/resolv.conf generated)
. 2018.03.10 20:52:45 - Flushing DNS
I 2018.03.10 20:52:46 - Checking route
I 2018.03.10 20:52:47 - Checking DNS
. 2018.03.10 20:52:47 - Checking DNS failed:
. 2018.03.10 20:52:47 - Checking DNS (2° try)
. 2018.03.10 20:52:49 - Checking DNS failed:
. 2018.03.10 20:52:49 - Checking DNS (3° try)
. 2018.03.10 20:52:51 - Checking DNS failed:
E 2018.03.10 20:52:51 - Checking DNS failed.
. 2018.03.10 20:52:51 - OpenVPN > Initialization Sequence Completed
! 2018.03.10 20:52:51 - Disconnecting
. 2018.03.10 20:52:51 - Sending management termination signal
. 2018.03.10 20:52:51 - Management - Send 'signal SIGTERM'
I 2018.03.10 20:52:52 - Break signal received. Shutdown. Hit again to force break.
. 2018.03.10 20:52:52 - Connection terminated.
. 2018.03.10 20:52:52 - DNS of the system restored to original settings (Rename method)
. 2018.03.10 20:52:52 - Shutdown in progress
I 2018.03.10 20:52:53 - Cancel requested.
! 2018.03.10 20:52:53 - Session terminated.
! 2018.03.10 20:52:54 - Logged out.
. 2018.03.10 20:52:54 - Shutdown complete

 



#2 LZ1

LZ1

    It's nice to be nice to nice people

  • Moderators
  • 1823 posts

Posted 11 March 2018 - 02:08 AM

Hello!

 

You may find this FAQ useful in that case.

 

With this man page perhaps particularly useful.

 

dns.check

  When the connection is established, if 'True' it try to resolve domain names that are resolved only by AirDNS server, to ensure that system is correctly using our DNS server.
  It's not mandatory to use our DNS server, but it's recommended to enjoy our Geolocation Routing service and avoid DNS blocks by your provider. Default: 'True'

 

It can sometimes also be useful to uncheck "Check Air Tunnel Works", if the DNS setting alone doesn't do the trick.

 

Also, you may benefit from trying out the TCP 443 protocol too :).

 

Also, 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 TheHellSite

TheHellSite

    Member

  • Members
  • PipPip
  • 14 posts

Posted 11 March 2018 - 08:03 PM

You might consider checking your MTU value with vpn disconnected.

I had the same problem. Feel free to take a look at my solution!

 

https://airvpn.org/topic/22896-route-check-dns-check-fails/#entry64707







Similar Topics Collapse


1 user(s) are reading this topic

0 members, 1 guests, 0 anonymous users

Servers online. Online Sessions: 14123 - BW: 47191 Mbit/sYour IP: 54.81.254.212Guest Access.