[Pdns-users] Strange behaviour of recursor cache on a particular domain

[GAVARRET, David]

bert hubert wrote on mercredi 14 juin 2006 19:29:
> 
> My feeling is that in this case, the melusine.eu people might have
> messed up previously, but that the problem is gone now and we are
> waiting for their (large) ttl to expire. 
> 
> But I might be wrong.

Just played with rec_control dump-cache option (great thing ! :) )

ns1:/u0# rec_control dump-cache /u0/ns1_cache_20060614
ns1:/u0# grep -i melusine.eu.org ns1_cache_20060614 

MELUSINE.EU.ORG. -150630 IN A 193.55.139.7
MELUSINE.EU.ORG. 93869 IN A 195.6.210.105
melusine.eu.org. 8271 IN NS ns.melusine.eu.org.
melusine.eu.org. 8271 IN NS ns.eu.org.
melusine.eu.org. 21412 IN SOA ns.melusine.eu.org.
hostmaster.melusine.eu.org. 2006060701 7200 3600 1209600 259200
NS.MELUSINE.eu.org. 56333 IN A 193.55.139.7

# dig +noall +answer @ns1 melusine.eu.org soa melusine.eu.org
melusine.eu.org.        21251   IN      SOA     ns.melusine.eu.org.
hostmaster.melusine.eu.org. 2006060701 7200 3600 1209600 259200
melusine.eu.org.        93708   IN      A       195.6.210.105

What does means the negative value of the first record in the cache (the
one not replied when quering the recursor) ? 
Is it a negative caching entry ? means that when the recursor tried to
"renew" the record, it didn't find that value ?

-- 
David