Innovate | Connect | Transform
ContactService statusUSD $

GICT knowledge base

Change GoDaddy Nameservers Without Losing DNS Dependencies

Published

DNS

Changing nameservers at GoDaddy delegates a registered domain to a DNS service. It can change where all of the domain’s DNS records are managed, affecting email and verification as well as the website. It does not transfer domain ownership or move files and mailboxes.

Prepare the new DNS service

Copy and review required A/AAAA, MX, TXT, aliases and verification records at the intended provider before switching. Use the nameservers assigned to the actual account. If using custom hosts under the domain, complete required host/glue registration first. Review any DNSSEC DS/key transition with the providers.

Change the delegation

  1. Sign in securely to GoDaddy Domain Portfolio and select the exact registered domain.
  2. Open DNS > Nameservers.
  3. Choose the intended provider setting. For external service, select the custom/own-nameservers option and enter the supplied nameserver hostnames, not website IP addresses.
  4. Review all entries, save and continue through the required confirmation.
  5. Complete any Domain Protection or identity-verification challenge through the verified account. Do not share one-time codes with an unsolicited helper.

Verify the whole service

Compare the resulting parent delegation with the intended nameservers, query those servers directly and then compare recursive responses. Test website TLS and authorized mail receiving/sending separately. An old zone visible in the GoDaddy editor may no longer be the public source once another provider is authoritative.

GoDaddy publishes update estimates, but a fixed 48-hour maximum is not a universal diagnostic rule. Wrong authoritative records, unavailable nameservers or a stale DNSSEC relationship need correction rather than passive waiting. Retain the previous configuration and old service during a planned transition where feasible.

Reference: GoDaddy nameserver changes and account verification.

Reviewed October 16, 2026. No domain, record, account protection or nameserver setting was changed.

Related guides

Account services are unavailable until the production backend is configured.