Unbound low cache hit rate

[New2This]

You need to add this to your unbound config if you want higher cache hits:

serve-expired-client-timeout: 0

Are you running your Unbound thru Dietpi?

 

[Gary_Dexter]

Are you running your Unbound thru Dietpi?

I am, yes

 

[New2This]

I am, yes

root@DietPi:~# unbound -V
Version 1.22.0
Are you running the same version ? Just trying to see if there an update on there...but Im coming up empty.

 

[Gary_Dexter]

I’m running 1.24.2

Why do you ask, out of interest

 

[New2This]

I’m running 1.24.2

Why do you ask, out of interest

Im trying to update . but it's still coming in as that version. I would like to update to the current version- like what your showing

unbound is already the newest version (1.22.0-2+deb13u1).

 

[Gary_Dexter]

You’re probably using the version that comes with Debian’s Repo - presume you’re running Debian Trixie?

Client Challenge

DietPi are testing using their own Repo to provide the latest available Unbound Update - however you can do this manually for now with the following steps:

cd /tmp

wget "https://dietpi.com/downloads/binaries/$G_DISTRO_NAME/unbound_$G_HW_ARCH_NAME.deb"

apt install ./"unbound_$G_HW_ARCH_NAME.deb"

 

[New2This]

You’re probably using the version that comes with Debian’s Repo - presume you’re running Debian Trixie?

Client Challenge

DietPi are testing using their own Repo to provide the latest available Unbound Update - however you can do this manually for now with the following steps:

cd /tmp

wget "https://dietpi.com/downloads/binaries/$G_DISTRO_NAME/unbound_$G_HW_ARCH_NAME.deb"

apt install ./"unbound_$G_HW_ARCH_NAME.deb"

Yes I am running that version.

Thank you for the info . Installing now

Version 1.24.2

 

[keef]

Thank you very much! This fixed my cache percentage. Now I am on max (83.5%) of last 7 days running unbound 1.23.0.
Thank you very much @John DeLuca for this thread.

Can I ask how you edited the config file?

 

[ZebMcKayhan]

Can I ask how you edited the config file?

One way is to write 'vx' in unbound manager CLI. It will prompt for restart unbound after to apply your changes.

 

[keef]

Yes.

Anything you don’t manually override in the Unbound config file will always use the default values as stipulated here:

unbound.conf(5) — Unbound 1.24.2 documentation

unbound.docs.nlnetlabs.nl

Does it matter where in the .conf file you add that line? After adding that line near the top my cache hit rate still hovers around 20%.

thanks

 

[keef]

I figured that out. I stopped and started unbound so it would read the .conf file again. Worked like a charm.

 

[Tech9]

This may increase the hit rate, but in general serving expired records before refresh is not very good idea.

 

[bluzfanmr1]

For anyone interested, here's the relevant link on this. The way I read it, Unbound continues to look for updated records while retaining the ability to serve soon to be stale or expired records, to maintain resolving. This new setting enabled new behavior while retaining the option to keep the previous behavior, if desired.

Serving Stale Data