Aguard home dns lookup speeds

[keef]

Hello. I have Adguard home running my NAS, Asus RT88U (304.388.11) and Unbound. Everything is co-operating nicely except dns look up speeds. I get:

156.154.70.1:53 378 ms
156.154.71.1:53 106 ms
1.0.0.1:53 94 ms
8.8.4.4:53 74 ms
156.154.70.5:53 56 ms
8.8.8.8:53 55 ms
1.1.1.1:53 54 ms
156.154.71.5:53 48 ms
192.168.50.1:53 1 ms

I have caching on within Adguard. It seems petty slow.

thanks

 

[dave14305]

156.154.70.1:53 378 ms
156.154.71.1:53 106 ms
156.154.70.5:53 56 ms
156.154.71.5:53 48 ms

Where do these come from?

 

[keef]

From the Average Upstream Response Time window on Adguard dashboard.

 

[Tech9]

and Unbound

Comes from your own resolver. You may see queries with >500ms response time.

 

[keef]

You are right, I have seen higher. That just seems so long.

thanks

 

[Tech9]

It was your choice. You can't compete with Google and Cloudflare cache with own resolver. One of the drawbacks when using Unbound as resolver. In my opinion it's not needed on a home network.

 

[dave14305]

From the Average Upstream Response Time window on Adguard dashboard.

I mean why is AGH talking to any of these upstream servers if you believe you have Unbound as the upstream server? Look at your AGH config.

 

[Tech9]

Look at your AGH config.

Definitely wrong AGH configuration. I had to wait for the morning coffee effect...
Redirecting to Unbound may actually increase the resolution time for uncached requests.

 

[bluzfanmr1]

If you are wanting to use Unbound exclusively, your settings have included other resolvers. I use Unbound with AGH and here is my upstream list using Unbound only:

[/router.asus.com/][::]:553
[/www.asusnetwork.net/][::]:553
[/www.asusrouter.com/][::]:553
[/use-application-dns.net/][::]:553
[/dns.resolver.arpa/][::]:553
[/lan/][::]:553
[//][::]:553
127.0.0.1:53535

Also, turn off AGH caching as Unbound will do the caching. Resolving is slower where I live and I've tried all options and this works best for me: