"ApplianSys' sales and support staff are perfect. They're like my friends now. I can simply ask for help from any one of them"
Naif Orabi, Network Administrator at TAIF Ministry Of Education, Saudi Arabia
"With DNSBOX, our previous IP conflict problems are non-existent."
Mike Neverdusky, CDE Lightband, USA
"We now have an extremely high up time. The system is very reliable, and our IT teams are now able to focus on the job in hand"
Richard Thomson, London Business School
"What we really needed was reliability, fault tolerance and support. DNSBOX gives us peace of mind..."
Mark Albutt, Technical Manager, Probrand Limited, UK
"The ApplianSys' DNSBOXes have been wonderful. I recommend them to everyone I know that has a DNS server."
Matt Niswonger, Techician at UltraTech Resources, USA

Protect Against Cache Poisoning with DNSSEC

Many organisations want to introduce DNSSEC to protect against cache poisoning which can result in your users being misdirected to malicious websites and/or disrupt services that rely on DNS such as email and VOIP.

DNSSEC uses strong public key cryptography to sign DNS data which can then be validated by a requesting server. The root DNS zone and a growing number of Top Level Domains now sign their DNS records using DNSSEC, which creates a ‘chain of trust’ to validate answers down to an individual record. Many ISPs and public DNS services, like Google DNS, can also now carry out this validation process and some governments have required their public sector agencies to implement DNSSEC – for example in the USA.

But… implementing and managing DNSSEC can be complicated, costly and time-consuming:

  • All your zones need to be signed for DNSSEC to be effective – a big task for large networks
  • DNSSEC keys need to be stored securely so that they cannot be changed maliciously
  • Keys also need to be periodically updated – known as ‘key rollover’.
  • Additional DNSSEC steps in DNS resolution may introduce unwanted latency

Automate DNSSEC Key Rollover

DNSSEC-Screenshot-smKey rollover is particularly complex and requires very careful administration. If you get key rollover wrong, keys which are no longer valid remain cached in other DNS servers around the world or are not synchronised with your own upstream servers. In such cases, clients using DNSSEC would be unable to resolve your records.

To avoid this, you need to manage at least two sets of two types of key – a Zone Signing Key (ZSK) and a Key Signing Key (KSK), one of each live and one marked as in ‘rollover state’ – for each zone. The rollover keys need to exist for 2x their Time to Live value. With lots to know and manage, manual key rollover is incredibly error-prone.

You need a solution that, like DNSBOX:

  • Automates DNSSEC key management and rollover
  • Automates zone signing for rapid implementation
  • Makes it easy to store DNSSEC keys securely
  • Uses a high performance resolver to mitigate the extra latency of DNSSEC requests

Next: Microsoft Integration >

Because DNSBOX is versatile and scalable, our customers around the world come in all shapes and sizes. ISPs, enterprises, government agencies and even internet registers simplify, control and protect their DDI services with DNSBOX.

How can we make your visit easier?


Give us a few details about your requirement and we'll make your life easier by serving the most relevant information.
I work in a...
I prefer to read...
GO