<div dir="ltr">On Tue, Aug 25, 2015 at 12:50 AM, Reindl Harald <span dir="ltr"><<a href="mailto:h.reindl@thelounge.net" target="_blank">h.reindl@thelounge.net</a>></span> wrote:<br><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><span class=""><br>
<br>
Am 25.08.2015 um 12:46 schrieb Harshith Mulky:<br>
</span><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><span class="">
I have a confusion on how the clients respond to and cache when<br>
particularly we receive negative replies from a DNS Server, particularly<br>
NXDOMAIN or SERVFAIL responses<br>
<br>
on the DNS Zone file we have these records<br>
$ORIGIN e164.arpa.<br>
@ IN SOA picardvm2.e164.arpa. e164-contacts.e164.arpa. (<br>
2002022404 ; serial<br>
3H ; refresh<br>
15 ; retry<br>
1w ; expire<br></span>
*3h* ; minimum<span class=""><br>
)<br>
<br>
so 3h is basically the amount of time clients are asked to cache<br>
negative results.<br>
<br>
Now on the client side at lwresd.conf, if I have<br>
<br>
max-ncache-ttl 300<br>
<br>
Will the client override the default 3h value sent as response from the<br>
DNS Sever for the zone e164.arpa<br>
</span></blockquote>
<br>
yes, that's the purpose of this setting<span class=""><br>
<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
How are Negative responses usually cached?<br>
</blockquote>
<br></span>
by TTL while in case of a SERVFAIL i am not sure if it get cached<br></blockquote><div><br></div><div>Only authoritative negative responses are cached. SERVFAILs are never authoritative, by definition.<br></div></div>--<br clear="all"><div><div class="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr">Kevin Oberman, Network Engineer, Retired<br>E-mail: <a href="mailto:rkoberman@gmail.com" target="_blank">rkoberman@gmail.com</a><br></div><div>PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683</div></div></div></div></div></div></div></div></div>