Register Custom Nameserver Hosts at GoDaddy

When a domain registered at GoDaddy needs nameservers within its own name, such as ns1.example.com for example.com, create the registrar’s custom hostname registration as required. This host/glue task differs from adding an ordinary A record and from changing the domain’s delegated nameservers.

Before adding the host

Confirm the authoritative service already exists, its real listener address and its allowed domain/registry requirements. Reserve example names and addresses for documentation only. Keep the nameserver’s authoritative address records consistent with the registered host data. A glue entry does not install DNS software, create hosted zones or open a firewall.

Use the current GoDaddy hostname controls

1. Sign in through GoDaddy’s verified site and open Domain Portfolio.
2. Select the parent domain, then open DNS > Hostnames.
3. Choose Add Hostname. Enter the host label in the form’s required format, such as ns1 rather than accidentally repeating the parent domain.
4. Supply the actual supported nameserver address and review any additional-address controls and registry restrictions.
5. Save, inspect the resulting hostname/address and complete any account verification requested.

Old screenshots used gear icons and Settings > Host Names; do not expect those labels in the current dashboard. Consult GoDaddy’s current instructions if the controls differ rather than editing unrelated zone NS records.

Verify before delegating

Check the host registration and authoritative nameserver answers for the intended zones. Then use the separate GoDaddy nameserver-change procedure when ready. Do not retire an old address until the registered host, authoritative address data and dependent delegations have been reviewed.

Provider readiness estimates and cached answers are not guarantees that every client has switched. Avoid repeated host deletion/recreation to force updates; preserve the previous values for recovery.

Reference: GoDaddy custom hostnames.

Reviewed October 16, 2026 against registrar documentation. No registrar account, host registration or delegation was changed.