Change a domain registered with us's nameservers when you want a different DNS service to answer for the domain. If you only need to point the website to a new server, changing the relevant A, AAAA or CNAME records may be sufficient instead.
IN THIS ARTICLE
01 Prepare the new DNS service
Obtain the exact nameserver hostnames from your current hosting or DNS service details. Use the nameservers assigned to the relevant service, especially if you have several hosting accounts. Do not copy old nameserver addresses from an unrelated article.
Before switching, copy all required website, mail, verification and subdomain records to the destination. Check DNSSEC and parent DS requirements if the domain is signed. A nameserver change does not move those records automatically.
02 Update the domain
- Sign in to your client area.
- Open Domains > My Domains and select the correct domain.
- Open its Nameservers or Manage Nameservers action.
- Choose the custom-nameserver option when entering the assigned hostnames. Use a default option only after checking that it resolves to the service you intend.
- Replace the list with the complete nameservers you will use and save with Change Nameservers or the displayed save action.
Enter hostnames such as ns1.example.net, without https://, a path or a port. The TLD and registrar determine allowed counts and validation. Private nameserver glue must already be registered where required.
03 Example: check delegation and the new authoritative server
On a computer with dig installed, replace these example names with your own domain and one nameserver assigned by the new provider. These commands only read DNS.
dig +trace example.com NS
dig @ns1.example.net example.com SOA +norecurse
dig @ns1.example.net example.com MX +norecurse
The trace lets you inspect the parent delegation. The direct queries check what the selected new server actually serves. Look for the authoritative-answer flag (aa) and the expected zone and mail records, then repeat the direct checks against every assigned nameserver. This does not by itself validate the DNSSEC chain.
Verify the authoritative DNS result
Reopen the domain and check the saved list. Then inspect public delegation and the records returned by each authoritative server. Different resolvers can retain older information until their caches expire.
Test the website, email and important subdomains after the change. Keep the old DNS service active through the planned transition so users with cached delegation still receive valid answers.
Why was my domain nameserver update refused?
Read the exact message. Domain status, registrar restrictions, invalid nameserver hosts or a pending operation may prevent the change. Avoid repeatedly switching between providers while investigating.
If the domain is registered elsewhere, change its nameservers at that registrar. Having a DNS zone or hosting account with us does not give us control of an external registration.