Jump to content
Not connected, Your IP: 18.234.55.154

Recommended Posts

​Hi everyone,

Signed up a couple of weeks ago and from the start I've been experiencing very slow DNS lookup. That is to say, webpages will pause on 'looking up example.com...' for 5-10 seconds.

​So far I have tried: adjusted buffers, changed MTU, rolled back TAP driver, experimental Eddie, disabled IPv6. Have tried multiple servers and different browsers with same results. Actual speeds are reasonable enough. Don't see anything untoward in the logs.

​I'm running experimental Eddie client on Windows 10. Router is ASUS RT-AC66U with Merlin firmware.

​Any suggestions? Thanks all.x

Share this post


Link to post

Hello!

 

You could also try the OpenNIC servers if you want .  Air supports them.


Moderators do not speak on behalf of AirVPN. Only the Official Staff account does. Please also do not run Tor Exit Servers behind AirVPN, 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.

Share this post


Link to post

Thanks, seems to be slow whatever server I use: Tried google, OpenNIC and OpenDNS. All slow when connected to AirVPN, fine when I disconnect.

Share this post


Link to post

Seeing the same problem here with windows 10 using eddie experimental but i think it's an issue with windows 10 though as I have tried other vpn clients and they all do the same, takes ages to resolve dns but once it's resolved it's fine.

Share this post


Link to post

I have slow resolution issues but it only happens  upon  disconnect/reconnect and such. 

Doesn't matter whether it is through Eddie, or OpenVPN directly

(Win10)

Share this post


Link to post

Here is one from me.  Interesting to note that although my TAP adapter  pulls  10.4.0.1  from DHCP when connecting to an AirVPN server,    nslookup appears to be using my primary adapters  DNS setting (which was set to 10.50.0.1)

 

Regardless of that,  nslookup is always instant upon disconnect/reconnect,  however  pinging a web site, or loading a site in a browser still results in that 5 - 10 second delay OP was complaining about.     I actually stopped using the Air client as well because connecting itself would take so long under both the normal and experimental clients.  (especially on the "checking route" part), oddly  it was almost instant  when I was using a wireless adapter vs my hard line.  Haven't tested that again recently though.

 

I may need to just set up a virtual machine to run a bunch of tests or something.

 

------------
Got answer:
    HEADER:
	opcode = QUERY, id = 1, rcode = NXDOMAIN
	header flags:  response, auth. answer, want recursion, recursion avail.
	questions = 1,  answers = 0,  authority records = 1,  additional = 0

    QUESTIONS:
	1.0.50.10.in-addr.arpa, type = PTR, class = IN
    AUTHORITY RECORDS:
    ->  10.IN-ADDR.ARPA
	ttl = 86400 (1 day)
	primary name server = 10.IN-ADDR.ARPA
	responsible mail addr = (root)
	serial  = 0
	refresh = 28800 (8 hours)
	retry   = 7200 (2 hours)
	expire  = 604800 (7 days)
	default TTL = 86400 (1 day)

------------
Server:  UnKnown
Address:  10.50.0.1

------------
Got answer:
    HEADER:
	opcode = QUERY, id = 2, rcode = NOERROR
	header flags:  response, want recursion, recursion avail.
	questions = 1,  answers = 1,  authority records = 6,  additional = 12

    QUESTIONS:
	airvpn.org, type = A, class = IN
    ANSWERS:
    ->  airvpn.org
	internet address = 213.152.180.16
	ttl = 728 (12 mins 8 secs)
    AUTHORITY RECORDS:
    ->  org
	nameserver = c0.org.afilias-nst.info
	ttl = 61739 (17 hours 8 mins 59 secs)
    ->  org
	nameserver = b0.org.afilias-nst.org
	ttl = 61739 (17 hours 8 mins 59 secs)
    ->  org
	nameserver = b2.org.afilias-nst.org
	ttl = 61739 (17 hours 8 mins 59 secs)
    ->  org
	nameserver = a0.org.afilias-nst.info
	ttl = 61739 (17 hours 8 mins 59 secs)
    ->  org
	nameserver = a2.org.afilias-nst.info
	ttl = 61739 (17 hours 8 mins 59 secs)
    ->  org
	nameserver = d0.org.afilias-nst.org
	ttl = 61739 (17 hours 8 mins 59 secs)
    ADDITIONAL RECORDS:
    ->  a0.org.afilias-nst.info
	internet address = 199.19.56.1
	ttl = 147704 (1 day 17 hours 1 min 44 secs)
    ->  a0.org.afilias-nst.info
	AAAA IPv6 address = 2001:500:e::1
	ttl = 147704 (1 day 17 hours 1 min 44 secs)
    ->  a2.org.afilias-nst.info
	internet address = 199.249.112.1
	ttl = 147704 (1 day 17 hours 1 min 44 secs)
    ->  a2.org.afilias-nst.info
	AAAA IPv6 address = 2001:500:40::1
	ttl = 147704 (1 day 17 hours 1 min 44 secs)
    ->  b0.org.afilias-nst.org
	internet address = 199.19.54.1
	ttl = 147704 (1 day 17 hours 1 min 44 secs)
    ->  b0.org.afilias-nst.org
	AAAA IPv6 address = 2001:500:c::1
	ttl = 147704 (1 day 17 hours 1 min 44 secs)
    ->  b2.org.afilias-nst.org
	internet address = 199.249.120.1
	ttl = 147704 (1 day 17 hours 1 min 44 secs)
    ->  b2.org.afilias-nst.org
	AAAA IPv6 address = 2001:500:48::1
	ttl = 147704 (1 day 17 hours 1 min 44 secs)
    ->  c0.org.afilias-nst.info
	internet address = 199.19.53.1
	ttl = 147704 (1 day 17 hours 1 min 44 secs)
    ->  c0.org.afilias-nst.info
	AAAA IPv6 address = 2001:500:b::1
	ttl = 147704 (1 day 17 hours 1 min 44 secs)
    ->  d0.org.afilias-nst.org
	internet address = 199.19.57.1
	ttl = 147704 (1 day 17 hours 1 min 44 secs)
    ->  d0.org.afilias-nst.org
	AAAA IPv6 address = 2001:500:f::1
	ttl = 147704 (1 day 17 hours 1 min 44 secs)

------------
------------
Got answer:
    HEADER:
	opcode = QUERY, id = 3, rcode = NOERROR
	header flags:  response, want recursion, recursion avail.
	questions = 1,  answers = 1,  authority records = 6,  additional = 12

    QUESTIONS:
	airvpn.org, type = AAAA, class = IN
    ANSWERS:
    ->  airvpn.org
	AAAA IPv6 address = 2001:1af8:4010:a08d:22::
	ttl = 2754 (45 mins 54 secs)
    AUTHORITY RECORDS:
    ->  org
	nameserver = a2.org.afilias-nst.info
	ttl = 61739 (17 hours 8 mins 59 secs)
    ->  org
	nameserver = b0.org.afilias-nst.org
	ttl = 61739 (17 hours 8 mins 59 secs)
    ->  org
	nameserver = a0.org.afilias-nst.info
	ttl = 61739 (17 hours 8 mins 59 secs)
    ->  org
	nameserver = c0.org.afilias-nst.info
	ttl = 61739 (17 hours 8 mins 59 secs)
    ->  org
	nameserver = b2.org.afilias-nst.org
	ttl = 61739 (17 hours 8 mins 59 secs)
    ->  org
	nameserver = d0.org.afilias-nst.org
	ttl = 61739 (17 hours 8 mins 59 secs)
    ADDITIONAL RECORDS:
    ->  a0.org.afilias-nst.info
	internet address = 199.19.56.1
	ttl = 147704 (1 day 17 hours 1 min 44 secs)
    ->  a0.org.afilias-nst.info
	AAAA IPv6 address = 2001:500:e::1
	ttl = 147704 (1 day 17 hours 1 min 44 secs)
    ->  a2.org.afilias-nst.info
	internet address = 199.249.112.1
	ttl = 147704 (1 day 17 hours 1 min 44 secs)
    ->  a2.org.afilias-nst.info
	AAAA IPv6 address = 2001:500:40::1
	ttl = 147704 (1 day 17 hours 1 min 44 secs)
    ->  b0.org.afilias-nst.org
	internet address = 199.19.54.1
	ttl = 147704 (1 day 17 hours 1 min 44 secs)
    ->  b0.org.afilias-nst.org
	AAAA IPv6 address = 2001:500:c::1
	ttl = 147704 (1 day 17 hours 1 min 44 secs)
    ->  b2.org.afilias-nst.org
	internet address = 199.249.120.1
	ttl = 147704 (1 day 17 hours 1 min 44 secs)
    ->  b2.org.afilias-nst.org
	AAAA IPv6 address = 2001:500:48::1
	ttl = 147704 (1 day 17 hours 1 min 44 secs)
    ->  c0.org.afilias-nst.info
	internet address = 199.19.53.1
	ttl = 147704 (1 day 17 hours 1 min 44 secs)
    ->  c0.org.afilias-nst.info
	AAAA IPv6 address = 2001:500:b::1
	ttl = 147704 (1 day 17 hours 1 min 44 secs)
    ->  d0.org.afilias-nst.org
	internet address = 199.19.57.1
	ttl = 147704 (1 day 17 hours 1 min 44 secs)
    ->  d0.org.afilias-nst.org
	AAAA IPv6 address = 2001:500:f::1
	ttl = 147704 (1 day 17 hours 1 min 44 secs)

------------
Name:    airvpn.org
Addresses:  2001:1af8:4010:a08d:22::
	  213.152.180.16


 

Share this post


Link to post

Both adapters had no IPv6 connectivity, I tried unchecking the protocol on them too.  I had to disconnect from OPenVPN and use the Airclient with the "disable ipv6" option to get it to work properly.

I set my physical adapter to 8.8.8.8  so this result should be coming from the TAP device.

 

Once again the nslookup results were instant,  but opening web sites or pinging took a few seconds to respond after initial connection was made.

------------
Got answer:
    HEADER:
	opcode = QUERY, id = 1, rcode = NXDOMAIN
	header flags:  response, auth. answer, want recursion, recursion avail.
	questions = 1,  answers = 0,  authority records = 1,  additional = 0

    QUESTIONS:
	1.0.4.10.in-addr.arpa, type = PTR, class = IN
    AUTHORITY RECORDS:
    ->  10.IN-ADDR.ARPA
	ttl = 86400 (1 day)
	primary name server = 10.IN-ADDR.ARPA
	responsible mail addr = (root)
	serial  = 0
	refresh = 28800 (8 hours)
	retry   = 7200 (2 hours)
	expire  = 604800 (7 days)
	default TTL = 86400 (1 day)

------------
Server:  UnKnown
Address:  10.4.0.1

------------
Got answer:
    HEADER:
	opcode = QUERY, id = 2, rcode = NOERROR
	header flags:  response, want recursion, recursion avail.
	questions = 1,  answers = 1,  authority records = 6,  additional = 12

    QUESTIONS:
	airvpn.org, type = A, class = IN
    ANSWERS:
    ->  airvpn.org
	internet address = 213.152.180.16
	ttl = 3575 (59 mins 35 secs)
    AUTHORITY RECORDS:
    ->  org
	nameserver = a2.org.afilias-nst.info
	ttl = 106023 (1 day 5 hours 27 mins 3 secs)
    ->  org
	nameserver = a0.org.afilias-nst.info
	ttl = 106023 (1 day 5 hours 27 mins 3 secs)
    ->  org
	nameserver = b0.org.afilias-nst.org
	ttl = 106023 (1 day 5 hours 27 mins 3 secs)
    ->  org
	nameserver = d0.org.afilias-nst.org
	ttl = 106023 (1 day 5 hours 27 mins 3 secs)
    ->  org
	nameserver = c0.org.afilias-nst.info
	ttl = 106023 (1 day 5 hours 27 mins 3 secs)
    ->  org
	nameserver = b2.org.afilias-nst.org
	ttl = 106023 (1 day 5 hours 27 mins 3 secs)
    ADDITIONAL RECORDS:
    ->  a0.org.afilias-nst.info
	internet address = 199.19.56.1
	ttl = 65050 (18 hours 4 mins 10 secs)
    ->  a0.org.afilias-nst.info
	AAAA IPv6 address = 2001:500:e::1
	ttl = 65050 (18 hours 4 mins 10 secs)
    ->  a2.org.afilias-nst.info
	internet address = 199.249.112.1
	ttl = 61105 (16 hours 58 mins 25 secs)
    ->  a2.org.afilias-nst.info
	AAAA IPv6 address = 2001:500:40::1
	ttl = 147499 (1 day 16 hours 58 mins 19 secs)
    ->  b0.org.afilias-nst.org
	internet address = 199.19.54.1
	ttl = 61099 (16 hours 58 mins 19 secs)
    ->  b0.org.afilias-nst.org
	AAAA IPv6 address = 2001:500:c::1
	ttl = 61099 (16 hours 58 mins 19 secs)
    ->  b2.org.afilias-nst.org
	internet address = 199.249.120.1
	ttl = 61099 (16 hours 58 mins 19 secs)
    ->  b2.org.afilias-nst.org
	AAAA IPv6 address = 2001:500:48::1
	ttl = 61099 (16 hours 58 mins 19 secs)
    ->  c0.org.afilias-nst.info
	internet address = 199.19.53.1
	ttl = 65050 (18 hours 4 mins 10 secs)
    ->  c0.org.afilias-nst.info
	AAAA IPv6 address = 2001:500:b::1
	ttl = 65050 (18 hours 4 mins 10 secs)
    ->  d0.org.afilias-nst.org
	internet address = 199.19.57.1
	ttl = 61099 (16 hours 58 mins 19 secs)
    ->  d0.org.afilias-nst.org
	AAAA IPv6 address = 2001:500:f::1
	ttl = 61099 (16 hours 58 mins 19 secs)

------------
------------
Got answer:
    HEADER:
	opcode = QUERY, id = 3, rcode = NOERROR
	header flags:  response, want recursion, recursion avail.
	questions = 1,  answers = 1,  authority records = 6,  additional = 12

    QUESTIONS:
	airvpn.org, type = AAAA, class = IN
    ANSWERS:
    ->  airvpn.org
	AAAA IPv6 address = 2001:1af8:4010:a08d:22::
	ttl = 3575 (59 mins 35 secs)
    AUTHORITY RECORDS:
    ->  org
	nameserver = d0.org.afilias-nst.org
	ttl = 106023 (1 day 5 hours 27 mins 3 secs)
    ->  org
	nameserver = b2.org.afilias-nst.org
	ttl = 106023 (1 day 5 hours 27 mins 3 secs)
    ->  org
	nameserver = a0.org.afilias-nst.info
	ttl = 106023 (1 day 5 hours 27 mins 3 secs)
    ->  org
	nameserver = c0.org.afilias-nst.info
	ttl = 106023 (1 day 5 hours 27 mins 3 secs)
    ->  org
	nameserver = a2.org.afilias-nst.info
	ttl = 106023 (1 day 5 hours 27 mins 3 secs)
    ->  org
	nameserver = b0.org.afilias-nst.org
	ttl = 106023 (1 day 5 hours 27 mins 3 secs)
    ADDITIONAL RECORDS:
    ->  a0.org.afilias-nst.info
	internet address = 199.19.56.1
	ttl = 65050 (18 hours 4 mins 10 secs)
    ->  a0.org.afilias-nst.info
	AAAA IPv6 address = 2001:500:e::1
	ttl = 65050 (18 hours 4 mins 10 secs)
    ->  a2.org.afilias-nst.info
	internet address = 199.249.112.1
	ttl = 61105 (16 hours 58 mins 25 secs)
    ->  a2.org.afilias-nst.info
	AAAA IPv6 address = 2001:500:40::1
	ttl = 147499 (1 day 16 hours 58 mins 19 secs)
    ->  b0.org.afilias-nst.org
	internet address = 199.19.54.1
	ttl = 61099 (16 hours 58 mins 19 secs)
    ->  b0.org.afilias-nst.org
	AAAA IPv6 address = 2001:500:c::1
	ttl = 61099 (16 hours 58 mins 19 secs)
    ->  b2.org.afilias-nst.org
	internet address = 199.249.120.1
	ttl = 61099 (16 hours 58 mins 19 secs)
    ->  b2.org.afilias-nst.org
	AAAA IPv6 address = 2001:500:48::1
	ttl = 61099 (16 hours 58 mins 19 secs)
    ->  c0.org.afilias-nst.info
	internet address = 199.19.53.1
	ttl = 65050 (18 hours 4 mins 10 secs)
    ->  c0.org.afilias-nst.info
	AAAA IPv6 address = 2001:500:b::1
	ttl = 65050 (18 hours 4 mins 10 secs)
    ->  d0.org.afilias-nst.org
	internet address = 199.19.57.1
	ttl = 61099 (16 hours 58 mins 19 secs)
    ->  d0.org.afilias-nst.org
	AAAA IPv6 address = 2001:500:f::1
	ttl = 61099 (16 hours 58 mins 19 secs)

------------
Name:    airvpn.org
Addresses:  2001:1af8:4010:a08d:22::
	  213.152.180.16


Share this post


Link to post

Something must be seriously broken on my machien then because I ran the "disable IPv6" tool and its still the same.

 

I even tried through OpenVPN again and it reverts to  queries using the google DNS (8.8.8.8) I set on my physical adapter..

 

despite that,  using  dnsleaktest.com  for instacne only shows my resolver as 1 server: 195.99-88-23.rdns.scalabledns.com

Share this post


Link to post

I too am experiencing slow DNS lookup. I am using eddie client 2.10.3 on Windows 10.

 

There isnt a problem when configuring the client to use googles DNS servers. When using googles server the resolution is lightning fast. 

 

I have checked nslookup and i was sending AAAA queries. I disabled ipv6 on all the adaptor using the checkbox, ran the reg fix and also checked this manually in the registry but still sending AAAA queries.

Share this post


Link to post

Alright so I installed VMware, setup a clean windows 10 install.

 

All that's installed are AirVPN app, and Cryptostorms app.

 

This is with no VPN.  just passing through my connecting on the Guest OS

 

------------
Got answer:
    HEADER:
	opcode = QUERY, id = 1, rcode = NXDOMAIN
	header flags:  response, want recursion, recursion avail.
	questions = 1,  answers = 0,  authority records = 1,  additional = 0

    QUESTIONS:
	2.126.168.192.in-addr.arpa, type = PTR, class = IN
    AUTHORITY RECORDS:
    ->  168.192.IN-ADDR.ARPA
	ttl = 5 (5 secs)
	primary name server = 168.192.IN-ADDR.ARPA
	responsible mail addr = (root)
	serial  = 0
	refresh = 28800 (8 hours)
	retry   = 7200 (2 hours)
	expire  = 604800 (7 days)
	default TTL = 86400 (1 day)

------------
Server:  UnKnown
Address:  192.168.126.2

------------
Got answer:
    HEADER:
	opcode = QUERY, id = 2, rcode = NOERROR
	header flags:  response, auth. answer
	questions = 1,  answers = 1,  authority records = 0,  additional = 0

    QUESTIONS:
	airvpn.org.localdomain, type = A, class = IN
    ANSWERS:
    ->  airvpn.org.localdomain
	internet address = 213.152.180.16
	ttl = 5 (5 secs)

------------
------------
Got answer:
    HEADER:
	opcode = QUERY, id = 3, rcode = NXDOMAIN
	header flags:  response, want recursion, recursion avail.
	questions = 1,  answers = 0,  authority records = 1,  additional = 0

    QUESTIONS:
	airvpn.org.localdomain, type = AAAA, class = IN
    AUTHORITY RECORDS:
    ->  (root)
	ttl = 5 (5 secs)
	primary name server = a.root-servers.net
	responsible mail addr = nstld.verisign-grs.com
	serial  = 2016122101
	refresh = 1800 (30 mins)
	retry   = 900 (15 mins)
	expire  = 604800 (7 days)
	default TTL = 86400 (1 day)

------------
Name:    airvpn.org.localdomain
Address:  213.152.180.16


 

Now this is when connected through the AirVPN app.  I changed no settings, so IPv6  disable is checked by default,  and I also ran microsofts  IPv6 disable tool you linked to earlier.

Interesting but probably irrelevant is as soon as I ran nslookup with the VPN Connected on the Guest OS,  my air connection on my HostOS  dropped.  lol

 

I have seen the same behavior when connecting to cryptostorm as well.   Something going on with the TAP that is not properly disabling  IPv6 ?

------------
Got answer:
    HEADER:
	opcode = QUERY, id = 1, rcode = NXDOMAIN
	header flags:  response, auth. answer, want recursion, recursion avail.
	questions = 1,  answers = 0,  authority records = 1,  additional = 0

    QUESTIONS:
	1.0.4.10.in-addr.arpa, type = PTR, class = IN
    AUTHORITY RECORDS:
    ->  10.IN-ADDR.ARPA
	ttl = 86400 (1 day)
	primary name server = 10.IN-ADDR.ARPA
	responsible mail addr = (root)
	serial  = 0
	refresh = 28800 (8 hours)
	retry   = 7200 (2 hours)
	expire  = 604800 (7 days)
	default TTL = 86400 (1 day)

------------
Server:  UnKnown
Address:  10.4.0.1

------------
Got answer:
    HEADER:
	opcode = QUERY, id = 2, rcode = NOERROR
	header flags:  response, want recursion, recursion avail.
	questions = 1,  answers = 1,  authority records = 6,  additional = 12

    QUESTIONS:
	airvpn.org, type = A, class = IN
    ANSWERS:
    ->  airvpn.org
	internet address = 213.152.180.16
	ttl = 2197 (36 mins 37 secs)
    AUTHORITY RECORDS:
    ->  org
	nameserver = a0.org.afilias-nst.info
	ttl = 29880 (8 hours 18 mins)
    ->  org
	nameserver = b0.org.afilias-nst.org
	ttl = 29880 (8 hours 18 mins)
    ->  org
	nameserver = a2.org.afilias-nst.info
	ttl = 29880 (8 hours 18 mins)
    ->  org
	nameserver = c0.org.afilias-nst.info
	ttl = 29880 (8 hours 18 mins)
    ->  org
	nameserver = d0.org.afilias-nst.org
	ttl = 29880 (8 hours 18 mins)
    ->  org
	nameserver = b2.org.afilias-nst.org
	ttl = 29880 (8 hours 18 mins)
    ADDITIONAL RECORDS:
    ->  a0.org.afilias-nst.info
	internet address = 199.19.56.1
	ttl = 59786 (16 hours 36 mins 26 secs)
    ->  a0.org.afilias-nst.info
	AAAA IPv6 address = 2001:500:e::1
	ttl = 59786 (16 hours 36 mins 26 secs)
    ->  a2.org.afilias-nst.info
	internet address = 199.249.112.1
	ttl = 146781 (1 day 16 hours 46 mins 21 secs)
    ->  a2.org.afilias-nst.info
	AAAA IPv6 address = 2001:500:40::1
	ttl = 49446 (13 hours 44 mins 6 secs)
    ->  b0.org.afilias-nst.org
	internet address = 199.19.54.1
	ttl = 123084 (1 day 10 hours 11 mins 24 secs)
    ->  b0.org.afilias-nst.org
	AAAA IPv6 address = 2001:500:c::1
	ttl = 123084 (1 day 10 hours 11 mins 24 secs)
    ->  b2.org.afilias-nst.org
	internet address = 199.249.120.1
	ttl = 49446 (13 hours 44 mins 6 secs)
    ->  b2.org.afilias-nst.org
	AAAA IPv6 address = 2001:500:48::1
	ttl = 146781 (1 day 16 hours 46 mins 21 secs)
    ->  c0.org.afilias-nst.info
	internet address = 199.19.53.1
	ttl = 63391 (17 hours 36 mins 31 secs)
    ->  c0.org.afilias-nst.info
	AAAA IPv6 address = 2001:500:b::1
	ttl = 63391 (17 hours 36 mins 31 secs)
    ->  d0.org.afilias-nst.org
	internet address = 199.19.57.1
	ttl = 49446 (13 hours 44 mins 6 secs)
    ->  d0.org.afilias-nst.org
	AAAA IPv6 address = 2001:500:f::1
	ttl = 146781 (1 day 16 hours 46 mins 21 secs)

------------
------------
Got answer:
    HEADER:
	opcode = QUERY, id = 3, rcode = NOERROR
	header flags:  response, want recursion, recursion avail.
	questions = 1,  answers = 1,  authority records = 6,  additional = 12

    QUESTIONS:
	airvpn.org, type = AAAA, class = IN
    ANSWERS:
    ->  airvpn.org
	AAAA IPv6 address = 2001:1af8:4010:a08d:22::
	ttl = 3393 (56 mins 33 secs)
    AUTHORITY RECORDS:
    ->  org
	nameserver = a2.org.afilias-nst.info
	ttl = 29880 (8 hours 18 mins)
    ->  org
	nameserver = a0.org.afilias-nst.info
	ttl = 29880 (8 hours 18 mins)
    ->  org
	nameserver = b0.org.afilias-nst.org
	ttl = 29880 (8 hours 18 mins)
    ->  org
	nameserver = d0.org.afilias-nst.org
	ttl = 29880 (8 hours 18 mins)
    ->  org
	nameserver = b2.org.afilias-nst.org
	ttl = 29880 (8 hours 18 mins)
    ->  org
	nameserver = c0.org.afilias-nst.info
	ttl = 29880 (8 hours 18 mins)
    ADDITIONAL RECORDS:
    ->  a0.org.afilias-nst.info
	internet address = 199.19.56.1
	ttl = 59786 (16 hours 36 mins 26 secs)
    ->  a0.org.afilias-nst.info
	AAAA IPv6 address = 2001:500:e::1
	ttl = 59786 (16 hours 36 mins 26 secs)
    ->  a2.org.afilias-nst.info
	internet address = 199.249.112.1
	ttl = 146781 (1 day 16 hours 46 mins 21 secs)
    ->  a2.org.afilias-nst.info
	AAAA IPv6 address = 2001:500:40::1
	ttl = 49446 (13 hours 44 mins 6 secs)
    ->  b0.org.afilias-nst.org
	internet address = 199.19.54.1
	ttl = 123084 (1 day 10 hours 11 mins 24 secs)
    ->  b0.org.afilias-nst.org
	AAAA IPv6 address = 2001:500:c::1
	ttl = 123084 (1 day 10 hours 11 mins 24 secs)
    ->  b2.org.afilias-nst.org
	internet address = 199.249.120.1
	ttl = 49446 (13 hours 44 mins 6 secs)
    ->  b2.org.afilias-nst.org
	AAAA IPv6 address = 2001:500:48::1
	ttl = 146781 (1 day 16 hours 46 mins 21 secs)
    ->  c0.org.afilias-nst.info
	internet address = 199.19.53.1
	ttl = 63391 (17 hours 36 mins 31 secs)
    ->  c0.org.afilias-nst.info
	AAAA IPv6 address = 2001:500:b::1
	ttl = 63391 (17 hours 36 mins 31 secs)
    ->  d0.org.afilias-nst.org
	internet address = 199.19.57.1
	ttl = 49446 (13 hours 44 mins 6 secs)
    ->  d0.org.afilias-nst.org
	AAAA IPv6 address = 2001:500:f::1
	ttl = 146781 (1 day 16 hours 46 mins 21 secs)

------------
Name:    airvpn.org
Addresses:  2001:1af8:4010:a08d:22::
	  213.152.180.16


Share this post


Link to post

Here's what I've done for testing, as far as DNS resolution times go.
-------------------

I disabled comodo  (I recently started using the Comodo guide instead of network lock - but this should not influence anything)

I dropped the VPN connection on my Host machine.   DNS resolution was instant (reverting to 8.8.8.8)

I connected to Air on the host machine,  10 - 13 seconds for DNS resolution to kick in after connecting.

Booted up my VM.  Still connected to Air, the pass-through Internet is using the Air connection on my Host already.

Connect to Air with my Guest OS on a different server -  DNS resolution pretty much instant. 

Disconnect from Air on the Guest

Disconnect from Air on the Host -  DNS resolution is instant (8.8.8.8)

Connect to Air on the Guest, over the hosts unprotected ISP connection
The connection took longer (14 seconds most of it spent on verifying route) however once connected DNS resolution on the Guest OS was very instant.  

Now back on the Host OS again.  I have flushed DNS, my firewall is off
Set my AirVPN client to verify tunnel, and Air DNS  to match my GuestOS  settings for eddie.

Connection took 34 seconds to complete.  The first ~10 were spent on getting to the "verifying route" portion of the connection.  The other 24 seconds were spend "verifying route".
DNS resolution DNS resolution was instant.   ** This may be because it sat on verifying route for so long and thus the usual lag time I've been noting had already passed?

I now disconnect and turn off  "check if tunnel works effectively" and  "Verifying Air DNS" options on the Host machine.   I again connect to AirVPN. The whole connection attempt took relatively  ~11 seconds.   DNS resolution again takes 13 seconds.


Personally getting sick of reinstalls and fresh starts to try and fix this issue.    There used to be a time where I could connect to  AirVPN, even using Network lock, verifying DNS/tunnel etc and it didn not take very long at all.    I don't know if its something about Windows 10  (I switched to it pretty much after it was released)  or what the deal is.

I don't know what the deal with IPv6 disabling is either, but as it stands now I think I'd rather "block" it via Comodo or something than fuss with it.  Because I  need it for internal LAN connectivity.  Windows relies on IPv6 for "easy" home networking now, homegroups, etc.  The best I can get performance wise it seems is to run traffic control through comodo and disable all the verification stuff in Air / Use OpenVPN.  Then just deal with the short  DNS hiccup time  upon reconnects.

 

------------

I'm going to do one more test later on when I have some time,  and plug in my wireless adapter turn on network lock, etc.   Because it seems like I get totally different behavior when using wireless.

Share this post


Link to post

 

I connected to Air on the host machine,  10 - 13 seconds for DNS resolution to kick in after connecting.

 

This always happens to me as well.  Always has.  In Windows 7, 8, 8.1, and 10.  I've just gotten used to it. Seems like it takes a second for all of the Firewall/WFP stuff to propagate or something.  But once that 10 seconds has passed, everything works smooth for me, and I have no further delays. 

Share this post


Link to post

​Hi all... Okay so I appear to have fixed this. Don't ask me why this worked and the first step may be unnecessary but it worked for me:

 

​1. Disable IPV6 everywhere: Both adapters, OS and Router. This on it's own didn't fix the problem.

​2. Set the TAP adapter to a lower metric than your network adaptor:

​1. Network connections -> Adapter Settings -> TAP-Windows Adapter V9 -> Properties -> Internet Protocol Version 4 (TCP/IPv4) -> Properties -> Advanced

​Uncheck Automatic Metric

Interface Metric == 14

2. Network connections -> Adapter Settings -> Ethernet -> Properties -> Internet Protocol Version 4 (TCP/IPv4) -> Properties -> Advanced

​Uncheck Automatic Metric

Interface Metric == 15

This second step instantly fixes the problem for me. If I set the metrics to the same value or automatic the problem instantly comes back.

​Let me know if this works for you and Happy Holidays xx

Share this post


Link to post

Hello!

 

Thank you for sharing your findings with us!


Moderators do not speak on behalf of AirVPN. Only the Official Staff account does. Please also do not run Tor Exit Servers behind AirVPN, 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.

Share this post


Link to post

During the summer I suddenly got this slow dns issue after a long time of use of AirVPN.

But everything works as before after disabling IPv6 and changing the interface metrics.

 

Thanks a lot!

 

/// Per

Share this post


Link to post

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
  • Security Check
    Play CAPTCHA Audio
    Refresh Image

×
×
  • Create New...