Skip to main content

What is DNSSEC? Protect your domain from spoofing

Published on July 3, 2026 9 min read

DNSSEC secures your DNS with digital signatures against spoofing and cache poisoning. Learn how it works and how to enable it for your domain.

Flat vector illustration: a figure secures a stack of servers with a shield and check mark, while a chain of padlocks links the domain through a globe to the root and a forged request is blocked.

DNSSEC is a security extension for the Domain Name System (DNS) that adds a digital signature to DNS answers. It lets the computer that looks up a domain name on your visitor's behalf check that the answer really comes from your domain and was not altered on the way. In this article you will learn what DNSSEC is, how it defends against DNS spoofing and cache poisoning, how it works through a chain of trust with DS and DNSKEY records, how to switch it on for your own domain, and how LJPc hosting takes care of that for you automatically.

What is DNSSEC?

DNSSEC stands for Domain Name System Security Extensions. DNS is the phone book of the internet: it translates a domain name into the right IP address, for example through the A record. The problem is that classic DNS has no built-in way to check whether an answer is genuine. A resolver, the DNS server that carries out the lookup for you, will in principle trust any answer that arrives.

DNSSEC solves this by attaching a digital signature to each answer. A resolver that validates DNSSEC can then confirm that the answer comes from the correct source and has not been tampered with. One thing is worth stressing here: DNSSEC proves that DNS data is authentic and unchanged, but it does not encrypt your DNS traffic. It makes the answers trustworthy, not secret. It does not stop DNS tunneling either, because there the attacker owns the domain.

Why does DNSSEC matter?

Without DNSSEC, an attacker can try to slip in fake DNS answers. This is called DNS spoofing, and when such a forged answer ends up in a resolver's cache, it becomes cache poisoning. The resolver then hands out the fake answer to everyone who asks for that domain, for as long as it stays cached.

The result is that visitors are quietly sent to the wrong server while they still see the correct domain name in their address bar. That opens the door to phishing, password theft and the interception of email. DNSSEC stops this attack from working: a resolver that checks the signature recognises a forged answer and rejects it.

DNSSEC complements other security measures. HTTPS protects the connection to your server, a CAA record controls which certificate authorities may issue certificates for your domain, and DNSSEC protects the lookup itself. Together they cover different layers. DNSSEC is also the foundation for DANE, which publishes the fingerprint of a mail server's certificate securely in DNS. You can read more about it in what is DANE.

How does DNSSEC work?

DNSSEC relies on digital signatures and on a chain of trust that reaches all the way up to the root of the DNS. A few terms help to make sense of what happens.

Signing with keys

When you enable DNSSEC, your zone is signed. Each set of records receives a digital signature, which is stored in an RRSIG record. Your A record and your other records still exist as before, but a signature is added to them.

The matching public keys are published in DNSKEY records. There are usually two roles: a Key Signing Key (KSK) that signs the set of keys, and a Zone Signing Key (ZSK) that signs the ordinary records. Some providers use a single combined key for this instead.

The chain of trust

The link to the outside world runs through the DS record. This is a short hash (a kind of fingerprint) of your key, and it does not live in your own zone but in the parent zone at the registry: the operator of the domain extension. For .nl, that operator is SIDN.

This creates a chain: the root of the DNS points to top-level domains such as .nl, .nl points through the DS record to your domain, and your domain signs its own records. The root has been signed since 2010 and acts as the trust anchor. A validating resolver checks the signatures step by step up to that root. If one link does not add up, the answer is rejected.

DNSSEC also signs the answer to a query for a name that does not exist. That is what the NSEC and NSEC3 records are for: they prove in a signed way that a record really is absent, so that an empty answer cannot be forged either.

The main DNSSEC records and what they do
RecordPurpose
DNSKEYHolds the public keys of your zone
RRSIGThe digital signature attached to each set of records
DSHash of your key in the parent zone, links you to the registry
NSEC / NSEC3Proves in a signed way that a record does not exist

How to activate DNSSEC

Activating DNSSEC always involves two sides. First you switch on signing at the party that manages your DNS, and then you publish the DS record at your registrar so the registry places it in the parent zone. When both are the same party, this is often a single action.

At LJPc hosting it happens automatically

If your domain is registered with LJPc and uses the LJPc nameservers (ns1.ljpc.network, ns2.ljpc.network and ns3.ljpc.network), we switch DNSSEC on automatically. Because LJPc manages both your DNS and your domain registration, we sign your zone and publish the DS record at the registry ourselves. This also applies to a new domain and to a domain you transfer to LJPc. You never have to copy keys or hashes by hand. If DNSSEC is already on at your current DNS provider, read the part about moving further down in this article first.

After that, we keep an eye on it: every half hour we check that the signing of your zone is still active. Want to see for yourself that it works? The section on checking DNSSEC below shows you how.

Does your domain use the LJPc nameservers while the registration is with another party? We take care of DNSSEC for domains registered with LJPc, because only then can we publish the DS record at the registry. A signed zone without a DS record adds nothing, because resolvers do not check the signatures in that case. Transfer your domain to LJPc and we add DNSSEC automatically. You can read how in transfer your domain to LJPc.

Is your domain registered with LJPc while another party manages your DNS? Then switch DNSSEC on at that party and contact support about the DS record at the registry.

At another DNS provider: step by step

  1. Make sure your domain uses the nameservers of your DNS provider. You can read more in the article about the NS record.
  2. Enable DNSSEC or zone signing at your DNS provider. It generates the keys, signs the zone and refreshes the signatures automatically.
  3. Publish the DS record (or the DNSKEY) at your registrar, so the registry adds your domain to the chain of trust.
  4. Afterwards, check that the chain is valid with a DNSSEC checking tool or a validating resolver.

Whether DNSSEC is possible depends on the domain extension. Most top-level domains now support it. For .nl, SIDN supports DNSSEC, and more than half of all .nl domains are already signed. SIDN uses modern, efficient keys based on ECDSA (algorithm 13). LJPc hosting also signs zones with algorithm 13, with a separate KSK and ZSK.

Checking DNSSEC and common mistakes

Checking your setup afterwards is important, because a DNSSEC error does not always show up straight away. Use an online checking tool, such as the website test at internet.nl, or run the command dig +dnssec yourdomain.nl and look for RRSIG lines and the AD flag (Authenticated Data). That flag means the resolver validated the answer successfully.

Most problems happen because the two sides do not match, or because DNSSEC is changed in the wrong order during a move. You will find more ways to track down an outage in troubleshoot DNS problems.

Common DNSSEC problems and how to solve them
SymptomCauseSolution
Site or email unreachable (SERVFAIL) after switching onThe DS record does not match the active key, or the signatures have expiredCheck that the DS record matches the current key and have your provider re-sign the zone
DNSSEC looks enabled but is not validatedThere is no DS record at the registrar yetPublish the DS record in the parent zone
Domain unreachable after your DNS moved to another partyThe old DS record is still at the registry, while the new nameservers use different keys or no signatures at allHave the old DS record removed at the registrar, or replaced by a DS record that matches the keys of the new party

DNSSEC when you move

Whether you need to do anything with DNSSEC when you move depends on what you are moving. The DS record at the registry must always match the keys of the party that signs your zone, and that is the party behind your nameservers.

  • Moving only the registration. If your nameservers stay the same, the same party keeps signing your zone and DNSSEC does not need to be switched off. Do check afterwards that DNSSEC is still active.
  • Moving your DNS to LJPc. This also happens when you transfer your domain to LJPc, because your domain then moves to the LJPc nameservers. If DNSSEC is on at your current DNS provider, have the DS record removed there first and wait for the TTL to pass: the time a DNS answer may be cached. Only then change your nameservers or start the transfer. If your domain is registered with LJPc, we then switch DNSSEC on automatically. The step-by-step plan is in change your nameservers.
  • Moving your DNS away from LJPc. If you change the nameservers of a domain registered with LJPc to another party in the customer portal, we remove the DS record at the registry automatically. Want DNSSEC at your new DNS provider? Switch it on there as soon as the new nameservers are active, and contact support about the new DS record.

Stuck, or want to be sure that DNSSEC is set up correctly for your domain? Feel free to contact LJPc hosting support.

Frequently asked questions

Does DNSSEC encrypt my DNS traffic?

No. DNSSEC proves that DNS answers are genuine and unchanged, but it does not encrypt the traffic. If you also want to encrypt your DNS lookups, you can use DNS over HTTPS (DoH) or DNS over TLS (DoT). That is separate from DNSSEC and works well alongside it.

What is the difference between a DNSKEY record and a DS record?

The DNSKEY record holds the public key of your own zone. The DS record lives in the parent zone at the registry and is a hash of that key. The DS record links your domain to the chain of trust, so the layer above can trust your key.

Do I still need DNSSEC if I already use HTTPS?

Yes. HTTPS secures the connection to your server once the correct address has been found. DNSSEC secures the lookup itself, that is, the route to that address. They protect different steps and complement each other.

What happens if DNSSEC is set up incorrectly?

Validating resolvers will reject the answers for your domain, and visitors will receive a SERVFAIL error. Your website and email can become unreachable as a result. That is why you should always check the chain after switching it on.

Is DNSSEC switched on automatically at LJPc hosting?

Yes, for domains that are registered with LJPc and use the LJPc nameservers. We sign your zone, publish the DS record at the registry and check every half hour that the signing is still active. You do not need to do anything yourself. If your domain is registered elsewhere, you get DNSSEC as soon as you transfer the domain to LJPc.

Do I need to switch off DNSSEC before I transfer my domain?

That depends on what you are moving. If your nameservers stay the same and you only move the registration, DNSSEC can stay on. If your DNS moves to another party, including a transfer to LJPc, have the old DS record removed first and wait for the TTL to pass before the nameservers change. If you change the nameservers at LJPc to another party, we remove the DS record automatically.

Does .nl support DNSSEC?

Yes. SIDN, the operator of the .nl domain, supports DNSSEC, and more than half of all .nl domains are now signed. Most other top-level domains support DNSSEC as well.

Prefer to talk to someone?

We are also happy to answer your questions personally. Schedule a free consultation or call us directly. We are glad to think along with you.

Stay up to date with recent developments! Subscribe and receive our newsletter Signing up...