Introduction

A lame delegation means a nameserver is listed as authoritative for a domain but does not actually answer authoritatively for that zone. That creates confusing DNS failures because the delegation looks present while queries still fail, time out, or return inconsistent data depending on resolver choice. The right fix is to align registrar delegation, glue, and actual authoritative zone service.

Symptoms

  • DNS checks report lame delegation for one or more nameservers
  • Some resolvers return answers while others time out or fail
  • The problem started after changing DNS providers or nameserver assignments
  • NS records look correct in one place, but the delegated servers do not serve the zone properly
  • Domain verification, email, or website resolution behaves inconsistently across networks

Common Causes

  • The registrar delegates the domain to nameservers that do not host the zone
  • Glue records are stale or point to the wrong IP addresses
  • The zone exists on one DNS provider, but delegation still references a previous provider
  • Hidden-primary or secondary setups were changed without updating public delegation
  • Firewall or network restrictions block authoritative responses from the delegated server

Step-by-Step Fix

  1. Query the delegated nameservers directly and confirm whether they answer authoritatively for the domain.
  2. Compare registrar-level nameserver delegation with the provider actually hosting the zone data.
  3. Check glue records for in-bailiwick nameservers and verify their IP addresses still match the live DNS service.
  4. Review whether a provider migration or partial cutover left the zone active in one place but delegated elsewhere.
  5. Confirm every delegated authoritative server has the current zone loaded and reachable over the network.
  6. Remove stale nameserver references rather than leaving resolvers to hit servers that are no longer authoritative.
  7. Recheck SOA and NS consistency after corrections so the delegation path is internally aligned.
  8. Validate website, mail, and verification records after the delegation issue is fixed because lame setups often mask wider drift.
  9. Document registrar access and delegation ownership so future DNS provider changes are performed as one coordinated cutover.