<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=utf-8"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
.MsoChpDefault
{mso-style-type:export-only;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:70.85pt 70.85pt 2.0cm 70.85pt;}
div.WordSection1
{page:WordSection1;}
--></style></head><body lang=DE link=blue vlink="#954F72"><div class=WordSection1><p class=MsoNormal>Hi George,<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>would it be an Option to add a configuration setting to the backend configuration saying whether TTL should be applied or not? It will simplify the Cache handling.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Bye<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Gesendet von <a href="https://go.microsoft.com/fwlink/?LinkId=550986">Mail</a> für Windows 10</p><p class=MsoNormal><o:p> </o:p></p><div style='mso-element:para-border-div;border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=MsoNormal style='border:none;padding:0cm'><b>Von: </b><a href="mailto:george@nlnetlabs.nl">George Thessalonikefs</a><br><b>Gesendet: </b>Mittwoch, 12. Februar 2020 18:11<br><b>An: </b><a href="mailto:talk.about@gmx.de">Talkabout</a>; <a href="mailto:unbound-users@lists.nlnetlabs.nl">unbound-users@lists.nlnetlabs.nl</a><br><b>Betreff: </b>Re: AW: AW: Unbound - Shared Cache</p></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Hi Peter,</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>On 12/02/2020 12:59, Talkabout wrote:</p><p class=MsoNormal>> Hi George,</p><p class=MsoNormal>> </p><p class=MsoNormal>> </p><p class=MsoNormal>> </p><p class=MsoNormal>> Maybe it’s stupid but it still not completely clear for me. As Unbound</p><p class=MsoNormal>> knows when a particular entry Needs to be invalidated (based on the</p><p class=MsoNormal>> configuration it received upon load) Setting the TTL via EXPIRE would</p><p class=MsoNormal>> also work for the case you mentioned (serving outdated entries based on</p><p class=MsoNormal>> Unbound configuration). Maybe I am missing something?</p><p class=MsoNormal>You are right that this could work but it may also be the case that you</p><p class=MsoNormal>want to turn on (or reconfigure) serve-expired on the fly through</p><p class=MsoNormal>unbound-control.</p><p class=MsoNormal>In that case you would like to have the expired records still lying around.</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Best regards,</p><p class=MsoNormal>-- George</p></div></body></html>