I thank you all for providing me such valuable information on DNS Negative
Caching
I would have never thought that so many things would be Applied in deciding
what would be cached
I once again thank each one of you and appreciate for the time and valuable
feedback
Cheers
Harshith
> F
I have a feeling that the discussion regarding SOA fields didn’t really answer
your question, Harshith.
Yes, negative results (NXDOMAIN) are usually cached for the amount of time
specified in the last field of the SOA. This field was originally named
“Minimum”, but is since used for NXDOMAIN TT
On Aug 28, 2015, at 5:27 PM, Barry Margolin wrote:
> Note that if a server is authoritative-only, caching is mostly
> irrelevant, so the negative cache TTL doesn't much apply. In this case,
> the SOA Minimum is just being used as the default TTL.
No, that is not correct. When responding negati
On 2015-08-28 14:15, Darcy Kevin (FCA) wrote:
As you pointed out (correctly), this isn't an issue which affects anything that goes "on the
wire", e.g. master-slave replication via AXFR/IXFR, since, "on the wire" the TTL is
always included with the RR. It's only an issue for how the zone files a
In article ,
"Darcy Kevin (FCA)" wrote:
> Negative-caching TTL and regular TTL have little to do with each other; it's
> not a reasonable assumption that one should stand in as a default for the
> other.
True, but that's water long under the bridge.
Note that if a server is authoritative-onl
ot;
errors in their logs, every time named loads or reloads the zones.
- Kevin
-Original Message-
From: bind-users-boun...@lists.isc.org
[mailto:bind-users-boun...@lists.isc.org] On Behalf Of Matus UHLAR - fantomas
Sent: Friday, August 28, 2015 3:49 PM
To: bind-users@lists.isc.org
On 28.08.15 17:32, Darcy Kevin (FCA) wrote:
RFC 2308 said that the use of the last field of the SOA to set
negative-caching TTL is "the new defined meaning of the SOA minimum
field". So you can *call* it "minimum", but it is *actually* supposed to
function as something else...
Eventually I hope
In article ,
"Darcy Kevin (FCA)" wrote:
> What's in a name? :-)
>
> RFC 2308 said that the use of the last field of the SOA to set
> negative-caching TTL is "the new defined meaning of the SOA minimum field".
> So you can *call* it "minimum", but it is *actually* supposed to function as
> so
sers-boun...@lists.isc.org] On Behalf Of Chris Buxton
Sent: Friday, August 28, 2015 11:06 AM
To: BIND Users
Subject: Re: DNS Negative Caching
> Is that really still true? I thought that use of the Minimum field
> went away when it was changed to be the negative cache TTL.
Barry,
Yes, i
> Is that really still true? I thought that use of the Minimum field went
> away when it was changed to be the negative cache TTL.
Barry,
Yes, it’s still true. If you don’t set a default TTL, then the last field of
the SOA record does double duty as both a default TTL and a negative caching
TT
In article ,
Alan Clegg wrote:
> > on the DNS Zone file we have these records
> > $ORIGIN e164.arpa.
> > @ IN SOA picardvm2.e164.arpa. e164-contacts.e164.arpa. (
> > 2002022404 ; serial
> >
On 8/27/15 10:24 AM, Reindl Harald wrote:
>> I wasn't really following this thread, but now that I see this, I would
>> like to add that the "expire" timer is also used as the default TTL for
>> resource records that do not have one specified, and if there is not an
>> explicit $TTL statement in t
Am 27.08.2015 um 16:08 schrieb Alan Clegg:
on the DNS Zone file we have these records
$ORIGIN e164.arpa.
@ IN SOA picardvm2.e164.arpa. e164-contacts.e164.arpa. (
2002022404 ; serial
> on the DNS Zone file we have these records
> $ORIGIN e164.arpa.
> @ IN SOA picardvm2.e164.arpa. e164-contacts.e164.arpa. (
> 2002022404 ; serial
> 3H ; refresh
>
On Tue, Aug 25, 2015 at 12:50 AM, Reindl Harald
wrote:
>
>
> Am 25.08.2015 um 12:46 schrieb Harshith Mulky:
>
>> I have a confusion on how the clients respond to and cache when
>> particularly we receive negative replies from a DNS Server, particularly
>> NXDOMAIN or SERVFAIL responses
>>
>> on t
Am 25.08.2015 um 12:46 schrieb Harshith Mulky:
I have a confusion on how the clients respond to and cache when
particularly we receive negative replies from a DNS Server, particularly
NXDOMAIN or SERVFAIL responses
on the DNS Zone file we have these records
$ORIGIN e164.arpa.
@ IN SOA p
I have a confusion on how the clients respond to and cache when particularly we
receive negative replies from a DNS Server, particularly NXDOMAIN or SERVFAIL
responses
on the DNS Zone file we have these records
$ORIGIN e164.arpa.
@ IN SOA picardvm2.e164.arpa. e164-contacts.e164.arpa. (
17 matches
Mail list logo
