<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div dir="ltr"><meta http-equiv="content-type" content="text/html; charset=utf-8"><div>Hi <span style="-webkit-text-size-adjust: auto; caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0); background-color: rgb(255, 255, 255);">Yorgos,</span><div><font color="#000000"><span style="-webkit-text-size-adjust: auto; background-color: rgb(255, 255, 255);"><br></span></font></div><div><font color="#000000"><span style="-webkit-text-size-adjust: auto; background-color: rgb(255, 255, 255);">Nice, yes that DNSSEC issue does seem related!</span></font></div><div><font color="#000000"><span style="caret-color: rgb(0, 0, 0); -webkit-text-size-adjust: auto; background-color: rgb(255, 255, 255);">I notice the last comments were 6 months ago, but it has been marked for 1.22.</span></font></div></div><div><font color="#000000"><span style="caret-color: rgb(0, 0, 0); -webkit-text-size-adjust: auto; background-color: rgb(255, 255, 255);"><br></span></font></div><div><font color="#000000"><span style="caret-color: rgb(0, 0, 0); -webkit-text-size-adjust: auto; background-color: rgb(255, 255, 255);">Issac, in the meantime we should each try to document our specific cases with reproducible examples if possible (and reference the above issue).</span></font></div><div><font color="#000000"><span style="caret-color: rgb(0, 0, 0); -webkit-text-size-adjust: auto; background-color: rgb(255, 255, 255);"><br></span></font></div><div><font color="#000000"><span style="background-color: rgb(255, 255, 255);">Our issues <span style="-webkit-text-size-adjust: auto;">may</span> prove to be easier to start with.</span></font></div><div><span style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0); -webkit-text-size-adjust: auto; background-color: rgb(255, 255, 255);"> </span></div><div>Thanks again for your help.</div><div>Andy.</div><div><br></div><div dir="ltr"><br><blockquote type="cite">On 1 Aug 2024, at 16:35, Yorgos Thessalonikefs via Unbound-users <unbound-users@lists.nlnetlabs.nl> wrote:<br><br></blockquote></div><blockquote type="cite"><div dir="ltr"><span>Hi Andy, Issac,</span><br><span></span><br><span>Maybe you are both hitting a variation of</span><br><span>https://github.com/NLnetLabs/unbound/issues/994.</span><br><span>Namely, Unbound when resolving will try to update the cache with new data even if the stale data would have been more useful.</span><br><span>There is ongoing work to make Unbound more careful with replacing cached content when serve-expired is used.</span><br><span></span><br><span>Best regards,</span><br><span>-- Yorgos</span><br><span></span><br><span>On 01/08/2024 04:46, Andy Lemin via Unbound-users wrote:</span><br><blockquote type="cite"><span>Hi,</span><br></blockquote><blockquote type="cite"><span>I have a similar experience, where prefetch seems to poison the cache with negative responses.</span><br></blockquote><blockquote type="cite"><span>This is a good read; https://unbound.docs.nlnetlabs.nl/en/latest/topics/core/serve-stale.html <https://unbound.docs.nlnetlabs.nl/en/latest/topics/core/serve-stale.html></span><br></blockquote><blockquote type="cite"><span>Can any one clarify a parameter combination which allows immediate cache responses, and which tells prefetch to always ignore negative responses?</span><br></blockquote><blockquote type="cite"><span>I wonder if taking the advice of the above article (and being mindful of this https://github.com/NLnetLabs/unbound/issues/533 <https://github.com/NLnetLabs/unbound/issues/533> it is possible to get this working). Just can’t figure out how to force prefetch to ignore negative responses.</span><br></blockquote><blockquote type="cite"><span>Please share your results :)</span><br></blockquote><blockquote type="cite"><span>Andy.</span><br></blockquote><blockquote type="cite"><blockquote type="cite"><span>On 31 Jul 2024, at 20:33, sir izake via Unbound-users <unbound-users@lists.nlnetlabs.nl> wrote:</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span></span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span></span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>Hi</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>I have installed unbound version: 1.20.0 on a FreeBSD 14 server. This was working fine until the server lost internet connectivity to the upstream internet provider. Prior to this the average cache hit rate on the server was 99.0% with only 1% recursive replies.</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>Part of my unbound.conf file is shown below</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span></span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>server: prefetch: yes serve-expired: yes</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span># serve-expired-ttl: 0</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span> # serve-expired-ttl-reset: no</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>After loss of internet average cache hit rate has reduced to 14% whiles recursive queries is showing 86% (still internet is not restored)</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>My expectation is</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>Caching server should continue to serve expired and keep the cache hit rate high because the serve-expired-ttl is default</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>(meaning it should continue serving cached content until upstream is restored).</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>My observation is the opposite. Is there anything I am missing? How can i ensure that the caching server will continue serving cache data several days after upstream</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>internet is lost</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>Regards</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>Isaac</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span></span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span></span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span></span><br></blockquote></blockquote></div></blockquote></div></body></html>