DNS Name resolution from 10.4.0.1 seems to fail randomly after working for hours or days

[AirBR 1]

Hi,

  I've noticed that DNS Name resolution from 10.4.0.1 seems to fail infrequently but it does so none the less.

 

I have my router configured to use 10.4.0.1 as the sole DNS server - and occasionally - but for no reason i can find - name resolution will simply stop working for SOME sites.

 

Using the routers built in DNS query tool during an "outage" i lookup cnet.com for example and get the following:-

 

Host "cnet.com" could not be resolved.

Timings

ame server Query time 10.4.0.1 31 msec

 

 

So from that i can see that the query is going to 10.4.0.1, that it is responding but it is not resolving cnet.com

 

If i simply wait and do nothing for a few minutes and try again it starts to work and i'll get the following (again for cnet.com):-

Results

Result Record type 64.30.228.118 A

Timings

Name server Query time 10.4.0.1 31 msec

 

Furthermore, whilst this is going on, I CAN get other sites to resolve with no issue so it seems limited to random sites and it's not a total outage.

 

During this time, the VPN is stable and nothing obvious is happening that i can see on my end and the outage usually lasts for 2 - 5 minutes but i can go quite a while without noticing a re occurrence of the issue.

 

Any ideas?

[kbps 29]

Hi,

  I've noticed that DNS Name resolution from 10.4.0.1 seems to fail infrequently but it does so none the less.

 

I have my router configured to use 10.4.0.1 as the sole DNS server - and occasionally - but for no reason i can find - name resolution will simply stop working for SOME sites.

 

Using the routers built in DNS query tool during an "outage" i lookup cnet.com for example and get the following:-

 

Host "cnet.com" could not be resolved.

Timings

ame server Query time 10.4.0.1 31 msec

 

 

So from that i can see that the query is going to 10.4.0.1, that it is responding but it is not resolving cnet.com

 

If i simply wait and do nothing for a few minutes and try again it starts to work and i'll get the following (again for cnet.com):-

Results

Result Record type 64.30.228.118 A

Timings

Name server Query time 10.4.0.1 31 msec

 

Furthermore, whilst this is going on, I CAN get other sites to resolve with no issue so it seems limited to random sites and it's not a total outage.

 

During this time, the VPN is stable and nothing obvious is happening that i can see on my end and the outage usually lasts for 2 - 5 minutes but i can go quite a while without noticing a re occurrence of the issue.

 

Any ideas?

 

 

I have been noticing something similar.  I use both Android and Eddie On Win 10.  Randomly a site will time out with the browser showing a DNS error message.  At first I thought that sites were down but It was happening too often.  A quick check at http://downforeveryoneorjustme.com/ show that the site is indeed up and reachable, just not from the Air server that I am using at the time. A reconnect to a different Air server fixes the issue. I am beginning to wonder if Air's DNS servers are struggling.

[hugomueller 13]

Same issue here on Diadema.

Win 8.1 x64

Eddie 2.11.15

 

edit:

I opened up a ticket.

 

edit2:

I found something out:

It seems that sometimes dns requests are sended to my router instead of using the airvpn dns. Airvpn dns is working fine but does not receive dns requests.

The dns requests to my router are blocked by dns leak protection so I get no result. after some minutes waiting it worked again. I changed nothing in the meanwhile...

 

how to reproduce it?

open cmd in windows

nslookup google.com

nslookup google.com 10.4.0.1

 

 

 

10.4.0.1 is the airvpn dns