reason for "expected covering NSEC3, got an exact match" ?

[Kalman Feher]

Ok now I see it.
The response appears ok, but the log entry is odd. I see the same on my test
box (9.7.1 not patched to P1 yet). A brief thread on this occurred earlier
in the year (archived here):
http://newsgroups.derkeiler.com/Archive/Comp/comp.protocols.dns.bind/2010-03
/msg00282.html
 


On 13/07/10 3:10 PM, "Gilles Massen" <gilles.massen at restena.lu> wrote:

> 
> Kalman Feher wrote:
>> It looks like normal NSEC to me, unless you are referring to an isolated
>> copy of the domain not accessible to the public:
> 
> Yes, indeed, sorry about that. I should keep my playgrounds tidier. The
> actual zone is located on nssec.restena.lu, and is publicly queriable
> (even with AXFR).
> 
> 
> Gilles
> 

-- 
Kal Feher | Melbourne IT