Hello,
(not a Bind related question !)
Last time I looked at Microsoft documentation I remember having seen that DNSSEC is for static files only,
*not* for “Active Directory integrated” domains !
If that is still true, I think the question about importing keys is irrelevant …
You would be needing Bind – from 9.7 onwards – for the DNS servers of the AD domains.
Bind can do the trick (DNSSEC + dynamic updating).
It would be sufficient to share the KSK, ZSK’s can be separate (as they are signed by the then shared KSK).
But is the an internal AD domain really an plausible attack vector for hackers ?
Kind regards,
Marc Lampo
Security Officer
EURid (for .eu)
Hello,
Yes, would be ideal …
I understand you want to make the Windows DNS service “DNSSEC capable”
(by feeding it KSK’s of domains that have the same name internally as externally).
However :
you are aware that Windows DNS service understands DNSSEC algorithm 5 (RSA/SHA-1 – NSEC) at most ?
à since the root zone is already algo 8 (RSA/SHA-256)
à since most tld’s are 7 or 8 and most with NSEC3
the Windows DNS service is going to treat most of DNSSEC’d name space as “unsigned” anyway …
(another argument to switch to Bind, internally ?)
Kind regards,
Marc Lampo
Security Officer
EURid (for .eu)
From: John Williams [mailto:john...@yahoo.com]
Sent: 29 June 2012 04:53 PM
To: Marc Lampo; bind-...@lists.isc.org
Subject: Re: BIND, DNSSEC & AD
The purpose behind this is not to protect the internal AD DNS from hijacking. But rather to allow internal clients to run DNSSEC related queries without having to reference external resolvers.
dig +dnssec somedomain
By the way, integrating BIND into AD will not be permitted. The AD staff will not allow that. That would be ideal though.