Unbound and client latency question

  • ATTENTION! As of November 1, 2020, you are not able to reply to threads 6 months after the thread is opened if there are more than 500 posts in the thread.
    Threads will not be locked, so posts may still be edited by their authors.
    Just start a new thread on the topic to post if you get an error message when trying to reply to a thread.

Markster

Senior Member
I have notice something peculiar that I have no answer to regarding DNS response latency running Unbound DNS.
I have my laptop connected directly to the router. When testing dig cnn.com on the router I get Query Time: 0ms.
That makes sense since unbound is caching cnn.com. When I perform the same dig command on my laptop the Query Time is 43ms. It is very consistent on the laptop, always 43 or 44ms for every cached record in unbound. I was sort of expecting the number on the client for cached entries to be much lower. When I try ping my router it comes back 0.4ms. Makes me think, what is the reason for this latency when entries are cached?

I have to revise this post. On 386.1 it looks as if dig somehost on the router does not return Query Time 0 anymore. I found that now it started to use 127.0.1.1 address since I have a quest network. I am sure this was different on 384.19 version. It is caching but locally getting a cache entries take 40ms.
My /etc/resolve.conf also has 127.0.1.1
 
Last edited:

dave14305

Part of the Furniture
I have to revise this post. On 386.1 it looks as if dig somehost on the router does not return Query Time 0 anymore. I found that now it started to use 127.0.1.1 address since I have a quest network. I am sure this was different on 384.19 version. It is caching but locally getting a cache entries take 40ms.
My /etc/resolve.conf also has 127.0.1.1
This would happen if DNS Privacy is active and you have the router set to use dnsmasq instead of the WAN DNS Servers (toggled from the Tools / Other Settings page).
 

Markster

Senior Member
I had to do hard reset back a week ago, you are sooo correct. I completely forgot about this setting.
Thanks for a quick response. Appreciate it.
 

Markster

Senior Member
After the fix above local dig works as expected returning Query Time: 0 for cached items. Local clients however still are above 40ms for the same cached entries.
 

dave14305

Part of the Furniture
Are the queries going to dnsmasq and then Unbound?
 

Markster

Senior Member
Are the queries going to dnsmasq and then Unbound?
dnsmasq is disabled. Using Unbound on port 53. I would be interested to hear from other with the similar setup what is their latency for the client. I am on version 386.1
 

Similar threads

Latest threads

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Top