Re: named querylog, cache hit

On May 19, 2009, at 2:12 AM, Anatoly Pugachev wrote: Hello! This is a request to enhancement. Is it possible to make named querylog log somehow if clients query hit the server cache or not, not regarding to other logged query options (like +EDC). In the absence of such logging from BIND, this

Re: named querylog, cache hit

At Tue, 19 May 2009 13:12:20 +0400, Anatoly Pugachev wrote: > This is a request to enhancement. > > Is it possible to make named querylog log somehow if clients query hit > the server cache or not, not regarding to other logged query options > (like +EDC). It's *possible* in that almost everyt

Re: "expected a exact match NSEC3, got a covering record"

In message <20090524194358.ga21...@frell.ambush.de>, Hauke Lampe writes: > Hello. > > I run a NSEC3-signed zone with many dynamic updates per day where > mailservers add RBL records and an hourly cronjob removes old entries. > > Several times a day I see queries for nonexistent names in the zon

"expected a exact match NSEC3, got a covering record"

Hello. I run a NSEC3-signed zone with many dynamic updates per day where mailservers add RBL records and an hourly cronjob removes old entries. Several times a day I see queries for nonexistent names in the zone fail. A typical query might start like this: | resolver: debug 1: createfetch: 17.2

dnssec-validation and root hints. why need to validate entries in root hints?

Hi! I have a DNSSEC isolated testlab and we simulated signining of a ccTLD. I and my friends already finished setting up the following: 1. client (resolvers) 2. DNS cache server (having a customized ROOT HINTS) 3. ROOT server (without root hints and with "." zone) 4. primary DNS server for "tld