[ldns-users] ldns-verify-zone bug

Jan-Piet Mens jpmens.dns at gmail.com
Wed Nov 21 16:21:50 UTC 2012

> [vagrant at pdns ~/pdns/regression-tests/ldns-verify-zone]$ ldns-verify-zone test.com
> original of NSEC3 hashed name could not be found at 81

I get the same error with 1.6.16, but the zone verifies correctly with
ldns 1.6.13:

        $ curl -o test.com http:// your url
        $ ldns-verify-zone test.com
        Checking: test.com.
        Checking: _underscore.test.com.
        Checking: c.test.com.
        Checking: b.c.test.com.
        Checking: a.b.c.test.com.
        Checking: *.a.b.c.test.com.
        Checking: counter.test.com.
        Checking: dc.test.com.
        Checking: _tcp.dc.test.com.
        Checking: _double._tcp.dc.test.com.
        Checking: _ldap._tcp.dc.test.com.
        Checking: enum.test.com.
        Checking: server1.test.com.
        Checking: test.test.com.
        Checking: *.test.test.com.
        Checking: www.test.test.com.
        Checking: very-long-txt.test.com.
        Checking: within-server.test.com.
        Checking: www.test.com.
        Zone is verified and complete



More information about the ldns-users mailing list