D
Deleted member 62525
Guest
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
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 by a moderator:
