OpenDNSSEC
Page Module:Infobox/styles.css has no content.
| OpenDNSSEC | |
|---|---|
| Initial release | July 30, 2009[1] |
| Written in | C, C++ |
| Operating system | Linux, FreeBSD, NetBSD, Mac OS X, Solaris |
| Type | DNSSEC |
| License | BSD |
| Website | www.opendnssec.org |
Script error: No such module "Check for conflicting parameters". Page Module:Infobox/styles.css has no content.
| SoftHSM | |
|---|---|
| Written in | C++ |
| Operating system | Linux, FreeBSD, NetBSD, Mac OS X |
| License | BSD |
| Website | www |
| Repository | github |
Script error: No such module "Check for conflicting parameters".
OpenDNSSEC is a computer program that manages the security of domain names on the Internet. The project intends to drive adoption of Domain Name System Security Extensions (DNSSEC) to further enhance Internet security. End-of-Life was announced on 3 October 2025, introducing its successor, Cascade.[4]
OpenDNSSEC was created as an open-source turn-key solution for DNSSEC. It secures DNS zone data just before it is published in an authoritative name server. OpenDNSSEC takes in unsigned zones, adds digital signatures and other records for DNSSEC and passes it on to the authoritative name servers for that zone. All keys are stored in a hardware security module and accessed via PKCS #11, a standard software interface for communicating with devices which hold cryptographic information and perform cryptographic functions. OpenDNSSEC can be paired with SoftHSM which provides a Software emulation of a hardware security module.[5]
OpenDNSSEC runs two dedicated daemons these are ods-enforcerd which acts as an enforcer Engine Daemon with the role of enforcing the KASP (Key and Signing Policy), and the ods-signerd which carries out actual signing of the zone. A DNS zone will failed to be signed if either process fail.
The ods-enforcer client program may be used to interact with the enforcer Engine and can be used to initiate such actions as a key rollover manually.
OpenDNSSEC uses the Botan cryptographic library, and SQLite or MySQL as database back-end. It is used on the .fr,[6].se, .dk, .nl,[7] .nz[8] and .uk top-level domains.[9]
See also
Lua error in mw.title.lua at line 404: bad argument #2 to 'title.new' (unrecognized namespace name 'Portal').
References
Page Template:Reflist/styles.css has no content.
- ^ Page Module:Citation/CS1/styles.css has no content."
NEWS". OpenDNSSEC. 1.0.0. 9 February 2010. Retrieved 18 June 2022 – via GitHub. - ^ Page Module:Citation/CS1/styles.css has no content."OpenDNSSEC News".
- ^ Page Module:Citation/CS1/styles.css has no content."SoftHSM 2.6.1".
- ^ Page Module:Citation/CS1/styles.css has no content."End-of-Life Roadmap for OpenDNSSEC". Opendnssec-announce. 3 October 2025. Retrieved 14 October 2025.
- ^ Page Module:Citation/CS1/styles.css has no content."OpenDNSSEC » SoftHSM". OpenDNSSEC.org. Retrieved 29 January 2024.
- ^ Page Module:Citation/CS1/styles.css has no content.Levigneron, Vincent. "DNSSEC: change of algorithm for the .fr zone". Afnic. Retrieved 30 January 2024.
- ^ Page Module:Citation/CS1/styles.css has no content.Ubbink, Stefan. "New DNSSEC algorithm for .nl". www.sidn.nl. Retrieved 10 February 2024.
- ^ Page Module:Citation/CS1/styles.css has no content."DNSSEC chain validation issue: technical incident report". InternetNZ. Retrieved 24 April 2024.
- ^ Page Module:Citation/CS1/styles.css has no content."OpenDNSSEC". Retrieved 17 September 2014.
External links
- Official website
- Page Module:Citation/CS1/styles.css has no content."OpenDNSSEC". Freecode.
- Page Module:Citation/CS1/styles.css has no content."SoftHSM". Freecode.
