• Monday 18 September 2017 Knowledge bank

    Just 4 weeks to go until the root KSK rollover

    check your DNSSEC trust anchors!

    Afbeelding van Just 4 weeks to go until the root KSK rollover: time to check your DNSSEC trust anchors!
    Read more
  • Thursday 5 July 2018 .nl domain name

    We're looking for startups with .nl domain names

    Share your story on sidn.nl

    Afbeelding van We're looking for startups with .nl domain names
    Read more
  • Sunday 8 April 2018 Knowledge bank

    Root zone rollover has implications for DNSSEC operators

    19 January 2017 In autumn 2017, ICANN initiated the rollover of the (KSK) pair for the root zone. The rollover involves renewing (i.e. replacing) the root zone's cryptographic key pair, which underpins the entire DNSSEC infrastructure. Renewing the key pair entails significant risk. Although it is very unlikely that anything will go wrong, an error could potentially render all internet domains (including non-signed domains) unreachable for all users and applications that rely on validating resolvers. The situation is similar at the local level. Validating resolver operators need to first add the new (public) key to the trust anchors on their servers, and subsequently remove the old key from their systems. If an operator fails to act, it won't be possible to validate any digital signatures beneath the top-level domains (TLDs) in the root zone. Then all internet domains will become unreachable for everyone relying on the resolver in question. RFC 5011 sets out a protocol for automatically installing the new (public) key as a trust anchor. The developers of the most widely used validating resolvers — BIND named, Unbound and OpenDNSSEC — all say that their software supports the protocol. The very dated Infoblox appliances don't support RFC 5011, meaning that Infoblox users face a fresh set of problems.

    Afbeelding van Root zone rollover has implications for DNSSEC operators
    Read more