On Sun, Jan 23, 2011 at 11:46:16PM +0100, Mark Huizer wrote:
> NSEC 5 3 86400 20110222021543 20110123021543 17462 verweg.com.
> W1WljyRcpbNl8kFEKAecpFXVr9lLi6i0I9DoFOvmPKMtDjfwrGLk4V1X9sWdet
> u/ohYFKdyap5wPcKuIPK87l0fYA4+rJCKsJyx3npDdYiH9D1nB6pIh43pWL+da
> 3dMd341Jqf6s8BVr39CfkzmVdzVpN7qkODc7TnQk
On Sun, 23 Jan 2011, Mark Huizer wrote:
> # DIG RRSIG @ns.example.com someentry.example.com
>
Keep in mind that the limit can sit in dig, not powerdns.
Especially occurs at older version from a default OS install.
So what about
$ drill ns.example.com someentry.example.com rrsig
--
Met vriende
Hello there,
I recently switched a machine from bind to PowerDNS, and 99% works like a charm.
My only issue is with a slave zone that uses DNSSEC. After changing the length
of the content field in the database (DNSKEY didn't fit otherwise), I'm left
with an issue with RRSIG records.
If I take