ANSWERED AirVPN DNS 10.4.0.1 very slow compared to 1.1.1.1

[freak 1]

When I change my manually-set DNS server from 10.4.0.1 (AirVPN) to 1.1.1.1 (Cloudflare), browsing gets significantly faster: I estimated ~5x..10x faster when opening up a new webpage in chrome, so from 'very slow' to 'instant'.
Any ideas - I like to use the AirVPN DNS server... ?

Info: Using Windows 10, connected to Matar

[OpenSourcerer 1435]

3 hours ago, freak said:

Add some extra info that might be helpful

Yeah, and still not enough. In Eddie > Logs tab, click the lifebelt icon and paste or upload the output here.

[Wolke68 5]

I try today Port 853 for 10.4.0.1 and goes really good 

[Flx 76]

10 hours ago, Wolke68 said:

I try today Port 853 for 10.4.0.1 and goes really good 

Can you post a screenshot so we don't die of NOT knowing Please
Thx

[Wolke68 5]

sure here it is. Sorry the Option for that Option are in German




 

 

 

[OpenSourcerer 1435]

That's a DNS-over-TLS port. Is your pfSense instance using that by any chance, or is it just another port for plain unencrypted DNS?

[Wolke68 5]

DNS resolver test show me 


Yes, your DNS resolver validates DNSSEC signatures.


so i thought itˋs up

[OpenSourcerer 1435]

DNSSEC validation is one thing, transferring DNS queries another. Guess I'll have to check myself.

[jovanka 0]

Kinda in the same problem here; pasting resolve times; only changed DNS. My first check was Diversion under MerlinFW on AC86U, but whatever I did, delay was still there. Changed DNS from 10.4.0.1 to 9.9.9.9 and voila. Tested on servers: AT, DE, CZ, CH.

time nslookup cnn.com
Server: 10.4.0.1
Address 1: 10.4.0.1

Name: cnn.com
Address 1: 151.101.1.67
Address 2: 151.101.193.67
Address 3: 151.101.129.67
Address 4: 151.101.65.67
Address 5: 2a04:4e42:200::323
Address 6: 2a04:4e42::323
Address 7: 2a04:4e42:600::323
Address 8: 2a04:4e42:400::323
real 0m 46.91s
user 0m 0.00s
sys 0m 0.00s

time nslookup cnn.com
Server: 9.9.9.9
Address 1: 9.9.9.9 dns9.quad9.net

Name: cnn.com
Address 1: 151.101.129.67
Address 2: 151.101.65.67
Address 3: 151.101.1.67
Address 4: 151.101.193.67
Address 5: 2a04:4e42:200::323
Address 6: 2a04:4e42::323
Address 7: 2a04:4e42:600::323
Address 8: 2a04:4e42:400::323
real 0m 0.19s
user 0m 0.00s
sys 0m 0.00s


Any additional input is appreciated! I'm kinda stuck if I don't change DNS 😕

EDIT: Retested, after every change of DNS servers applied "killall -1 dnsmasq". Still getting between 30 and 50 sec of delay when using 10.4.0.1 . Quad9 stays in 0.2-3sec.

[freak 1]

(I'm the one who posted the problem.)
I have tried to reproduce the problem of the slow DNS.
Good news: the problem has been resolved - I'm not sure what has changed, but the performance of the AirVPN DNS is excellent now.
* When browsing in Chrome, it 'feels' as fast as 1.1.1.1
* When running DNS Benchmark to measure the performance, the AirVPN DNSs are the fastest. See DNS Benchmark results below.
* When using "time nslookup", I typically see ~0.3..0.4 sec

$ time nslookup bbc.co.uk
Non-authoritative answer:
Server:  UnKnown
Address:  10.4.0.1

Name:    bbc.co.uk
Addresses:  2a04:4e42:400::81
          2a04:4e42::81
          2a04:4e42:200::81
          2a04:4e42:600::81
          151.101.64.81
          151.101.0.81
          151.101.128.81
          151.101.192.81


real    0m0.451s
user    0m0.015s
sys     0m0.077s

Thank you for your support! 

 

[Flx 76]

3 hours ago, freak said:

I'm not sure what has changed,

I can tell you what has not changed. Staff at AirVPN don't sit around all day drinking cappuccinos.

 

[OpenSourcerer 1435]

We can be 95% sure OP did something he/she doesn't usually do. The whole DNS problem was a local thing to begin with. If it wasn't, people would've noticed and posted the obligatory "I have the same issue" follow-ups. And I'm writing about tens or even hundreds of them, spanning over three or four threads, not just one other. I linked a particularly hilarious issue where everyone was truly affected, and this showed.

If it resurfaces, be sure to reply.