Fail

A DNSSEC signature on your records isn't valid yet

The short version

Check the clock on the signing server and re-sign the zone.

What it means

A signature on your zone's data has a start date (inception) in the future. Resolvers treat it as not valid yet. Signers usually backdate the start of a signature by an hour or so to allow for small clock differences, so a future start date points at a larger error.

Why it matters

Validating resolvers reject those records, so they fail for most visitors until the start date passes. The usual cause is a signing server whose clock is wrong, often after a restart or in a virtual machine without time synchronisation.

How to fix it

  1. Check the date and time on the signing server; turn on NTP time synchronisation.
  2. Re-sign the zone and reload it on every nameserver.
  3. If your DNS provider signs the zone, report the dates shown here to its support.

Check it worked

Run the DNSSEC and nameserver check again. Signatures should be valid now, with an expiry in the future.