How to fix DNSSEC (DS records) at Name.com

The DS record at your registrar tells the world your zone is DNSSEC-signed, and by which key. When it goes stale — classically after switching DNS providers — validating resolvers (Google 8.8.8.8, Cloudflare 1.1.1.1, most ISPs) return SERVFAIL and your site goes dark for those users while everything looks fine on your end.

⚠ Switching DNS providers on a DNSSEC-signed domain? Remove the DS record (or disable DNSSEC) at the registrar FIRST, and keep the old zone signed until the DS TTL has fully expired — changing nameservers while the old DS is cached makes validating resolvers return SERVFAIL (per Cloudflare's DNSSEC documentation).

Managing DS records manually

1. My Domains → the domain → Manage Nameservers → scroll to the bottom → DNSSEC Management.
2. Enter the DS values (Key Tag, Algorithm, Digest Type, Digest) from the DNS provider signing your zone.

Fixing a broken (bogus) chain

1. Confirm the break: our DNSSEC checker (or DNSViz) shows whether the DS at the registry matches the keys your DNS provider is actually signing with.
2. If you recently changed DNS providers: either publish the NEW provider's DS record here (get the values from their dashboard), or remove the DS entirely to unsign the domain — resolvers recover as caches expire.
3. If the DS is right but signatures expired, the fix is at your DNS provider (re-signing), not the registrar.

Name.com supports removing the DS record while keeping the domain.

⚠ Name.com's own nameservers don't support DNSSEC — DS entry only works when a third-party DNS provider signs the zone.

Steps verified against Name.com: managing DNSSEC and related Name.com docs on 2026-07-14.