Warning

Your NSEC3 settings use extra iterations or a salt

The short version

Set NSEC3 iterations to 0 and the salt to empty, as RFC 9276 recommends.

What it means

Your zone uses NSEC3 with extra hash iterations or a salt. NSEC3 proves that a name doesn't exist without listing your names openly; iterations and salt were meant to make that list harder to guess.

Why it matters

Extra iterations make every negative answer more work for resolvers and servers while adding almost no protection. Resolvers now treat zones with high iteration counts as unsigned or reject them, and RFC 9276 asks for zero iterations and no salt. The salt adds nothing either, because it is published in the zone itself.

How to fix it

  1. Check your DNS provider's DNSSEC settings for NSEC3 options; many already use 0 iterations.
  2. If you sign yourself, set iterations to 0 and the salt to - (empty) in your signer's NSEC3 settings.
  3. Re-sign the zone and reload it everywhere.

Check it worked

Run the DNSSEC and nameserver check. The denial line should say NSEC3 with no extra iterations and no salt.