Help & Troubleshooting
NS Record
What this is
NS records name the authoritative nameservers for a domain — the servers that actually hold and answer for its DNS zone. The registrar tells the parent zone which nameservers to delegate to; everything else in DNS depends on this being right.
How to read your result
Expect 2 or more nameservers, all belonging to the same DNS provider (the one whose control panel you actually edit records in). If these names surprise you, that explains why your DNS changes "don't work".
Common problems and how to fix them
NS points at one provider, but you edit records at another
How it shows up: Changes you make in a DNS control panel never take effect, no matter how long you wait.
How to fix it: Check the NS records to see who is really authoritative, then either edit records there, or update the nameservers at your registrar to the provider you want to use (which replaces the entire zone — recreate all records there first).
Registrar-level and zone-level NS records disagree
How it shows up: Intermittent, resolver-dependent behavior: some users see one set of records, others see another.
How to fix it: Make the NS set inside the zone identical to the delegation set at the registrar. After migrating DNS providers, update both places.
All nameservers in a single point of failure
How it shows up: When the DNS provider has an outage, the entire domain (web, mail, everything) goes down with it.
How to fix it: Use a provider with anycast nameservers on diverse networks (all major ones do this), or configure a secondary DNS provider for critical domains.