76
Tutorials and FAQs / Re: FRESH NEW AND IMPROVED GETDNS STUBBY AND UNBOUND AKA DNS PRIVACY
« on: July 18, 2020, 03:55:20 pm »
Nekromantik,
The DNS servers recommended in the original post were very slow for me (Texas).
I am using cloudflare (1.1.1.1 and 1.0.0.1) and recursion time usually ends up looking like this on the unbound statistics tab: 0.16 average and 0.1 median.
Cloudflare is by far the fastest DNS, and mixing it with google and quad 9 noticeable slows things down. When you throw NextDNS in the mix it gets even slower.
When I used the Directnupe's recommended A+ servers based in the USA it was averaging 1.5 seconds for a recursion. Those servers are based in East / West coast so it might be where I am located geographically.
I also messed around with the TTL on unbound and made it serve expired and it seemed to up the amount of cache hits significantly.
Using only Cloudflare with Stubby/Unbound cache I do not notice any difference from when I was just using unbound to forward to Cloudflare / Google servers from the general setting DNS area.
Cheers,
The DNS servers recommended in the original post were very slow for me (Texas).
I am using cloudflare (1.1.1.1 and 1.0.0.1) and recursion time usually ends up looking like this on the unbound statistics tab: 0.16 average and 0.1 median.
Cloudflare is by far the fastest DNS, and mixing it with google and quad 9 noticeable slows things down. When you throw NextDNS in the mix it gets even slower.
When I used the Directnupe's recommended A+ servers based in the USA it was averaging 1.5 seconds for a recursion. Those servers are based in East / West coast so it might be where I am located geographically.
I also messed around with the TTL on unbound and made it serve expired and it seemed to up the amount of cache hits significantly.
Using only Cloudflare with Stubby/Unbound cache I do not notice any difference from when I was just using unbound to forward to Cloudflare / Google servers from the general setting DNS area.
Cheers,