How do i change my name servers

You change nameservers at your domain registrar. Set the nameservers your registrar publishes for your domain to the ones you intend to use. If you want Hostworld to host your DNS for a cPanel hosting plan, point the domain to our nameservers, then manage the DNS records in cPanel’s Zone Editor.

Prepare the destination DNS zone first, plan for caches and TTLs, and handle DNSSEC if it is enabled. The change will not copy records for you and a missing zone causes downtime.

Before you start

• Know where your domain is registered. This is where nameserver changes are made. Nameserver delegation lives at the parent zone. It is not done in cPanel.
• Decide where your DNS will live after the change.
  • Hostworld cPanel hosting: use our nameservers and manage records in cPanel’s Zone Editor.
  • A Hostworld VPS: you can run authoritative DNS yourself. This needs glue and more setup.
  • Another DNS provider: use the nameservers they give you.
• Pre-create the DNS zone and all records at the destination. A, AAAA, CNAME, MX, TXT (SPF), DKIM and any others. Registrars do not copy records when you switch nameservers. Switching to an empty zone breaks your website and email.
• Plan DNSSEC. If DNSSEC is enabled, update the DS at the registrar to match the new provider’s signing, or temporarily remove the DS before the move. Leaving an old DS in place causes SERVFAIL.
• Lower TTLs in advance. Reducing TTL values on your current DNS speeds up cutover by shortening cache lifetimes.
• Check domain status. If the domain is on clientHold or serverHold at the registrar, it will not resolve regardless of nameserver settings. Clear the status first.
• If you plan custom nameservers (ns1.yourdomain.tld), register glue. Create host/child nameserver records at the registrar that map those hostnames to IPs.
• Do not edit /etc/resolv.conf on your server for this task. That changes lookups only for that one machine. It does not change your domain’s authoritative nameservers.

Step 1: Choose your target and gather the right nameserver set

Pick the destination and write down the exact nameserver hostnames you will use. Accuracy matters. A single typo prevents delegation.

• Hostworld cPanel hosting: use our nameservers:

  ns1.serverworld.uk
  ns2.serverworld.uk
  ns3.serverworld.uk
  ns4.serverworld.uk
  

• Your own DNS on a Hostworld VPS: you will use hostnames you control, for example:

  ns1.yourdomain.tld
  ns2.yourdomain.tld
  

  Register glue (host/child nameserver) for each one at the registrar before switching delegation.
• Another DNS provider: use the nameservers they give you.

Step 2: Build the destination DNS zone before switching

Set up the full zone at the destination so services work the moment caches expire.

• If you are pointing to Hostworld: once your domain is in your cPanel account, use Zone Editor to add or check A/AAAA, CNAME, MX, TXT, DKIM, DMARC and any SRV records you need. cPanel’s Zone Editor guide explains each record type. After delegation points to us, this is where you continue managing DNS.
• If you are running DNS on a VPS: add a zone file with your records and ensure your nameserver software answers for the domain.
• If you are moving to another provider: import or recreate records in their panel. Many have an “import zone” tool from a BIND file.

Keep a copy of your current records from the old provider in case you need to roll back.

Step 3: Handle DNSSEC safely

DNSSEC involves a DS record at the registrar and signing keys at your DNS provider. The order matters. The safe sequence is:

1. Disable DNSSEC at the registrar by removing the DS record, or prepare the new provider’s DS if they support an in-place key rollover.
2. Switch nameservers.
3. Enable DNSSEC again by adding the new DS at the registrar once the zone at the new provider is signed.

Not all registrars and providers automate DS updates. Expect manual steps. If you leave an old DS in place during a move, resolvers will see SERVFAIL for your domain until it is fixed.

Step 4: Reduce TTL values ahead of cutover

Lower TTLs one or two days before you change nameservers. This reduces how long old answers are cached by recursive resolvers.

• Lower the zone’s SOA minimum (if your provider exposes it) and the TTL on key records like the A/AAAA for the website and MX for email. Values around 300 seconds are common for a move.
• After the change completes, raise TTLs again to reduce query load.

Step 5: Change nameservers at your registrar

This is the actual delegation change. You do this in the registrar’s control panel for the domain.

• Enter the exact nameservers. For Hostworld cPanel hosting use:

  ns1.serverworld.uk
  ns2.serverworld.uk
  ns3.serverworld.uk
  ns4.serverworld.uk
  

• Save the changes fully. Many panels have a “Save” then a final “Confirm”. Incomplete saves are a common reason a change “doesn’t take”.
• Examples at popular registrars:
  • GoDaddy: see “Change my domain nameservers”.
  • Namecheap: see “How to Change DNS For a Domain”. Their guide also warns that host records are not auto added.

If you are moving to private nameservers like ns1.yourdomain.tld, register those hostnames with IPs at the registrar first. This is called registering host or child nameservers, or adding glue.

Step 6: Verify the delegation change from a terminal

Verification avoids guessing. You will check the parent zone and then trace resolution to the authoritative servers.

Install the basic DNS tools

This installs dig for DNS queries and whois for registrar data lookup.

Ubuntu 24.04:

sudo apt update
sudo apt install dnsutils whois

What this does: updates your package list, then installs the dig and whois utilities.

AlmaLinux 9:

sudo dnf install bind-utils whois

What this does: installs the dig utility from bind-utils and the whois client.

Check the parent’s view with whois

This shows which nameservers your registrar has published at the parent. Replace example.com with your domain.

whois example.com

What to look for: lines labelled Name Server. They should list the nameservers you entered. If they do not, go back to the registrar and finish the save or correct any typos. Also check for clientHold or serverHold statuses and clear them with the registrar if present.

Trace resolution with dig

This follows the chain from the root, through the TLD, to your authoritative nameservers.

dig +trace example.com

What to look for: near the end, you should see an answer from your chosen authoritative nameservers. If the trace still shows the old provider after an hour or two, check that the registrar change was confirmed. New delegation at the parent is usually visible quickly, though caches of your old records can persist until their TTLs expire.

Confirm NS consistency

All authoritative servers should serve the same NS set for your zone. Inconsistencies can cause intermittent resolution.

dig NS example.com
dig NS example.com @ns1.serverworld.uk
dig NS example.com @ns2.serverworld.uk

What to look for: the NS records returned by each authoritative server should match, and should match what the parent lists in whois. If they differ, update your zone to bring them into line.

Step 7: Re-enable DNSSEC (if you use it)

Once the new provider is serving your zone and you have verified resolution, enable DNSSEC again. Add the DS record at the registrar that corresponds to the DNSKEY in the new zone. Follow your provider’s guidance. If the registrar or provider does not support automation, you will copy the DS fields manually.

Step 8: Raise TTLs and tidy up

• Raise TTLs on key records back to normal values after traffic has moved cleanly.
• Remove the old zone from the previous DNS provider to avoid drift.
• Test website and email from multiple networks. For email, confirm MX, SPF, DKIM and DMARC are present and correct.

Optional: Run your own authoritative DNS on a Hostworld VPS

If you prefer to run DNS yourself on a VPS, do the hostnames and glue work before switching the domain to use them. The service name differs by OS.

Install and start BIND

Ubuntu 24.04:

sudo apt update
sudo apt install bind9
sudo systemctl enable --now bind9
sudo systemctl status bind9

What this does: installs the BIND DNS server, enables it to start on boot and starts it now. The status command confirms it is running.

AlmaLinux 9:

sudo dnf install bind bind-utils
sudo systemctl enable --now named
sudo systemctl status named

What this does: installs BIND and its tools, enables the named service to start on boot and starts it now. The status command confirms it is running.

Open DNS ports on the VPS firewall

DNS uses UDP and TCP on port 53. If you run a firewall, allow both protocols.

Ubuntu 24.04 with UFW:

sudo ufw allow 53/udp
sudo ufw allow 53/tcp
sudo ufw status

What this does: opens UDP and TCP port 53 then shows the firewall rules. If UFW is not in use, skip this step.

AlmaLinux 9 with firewalld:

sudo firewall-cmd --add-service=dns --permanent
sudo firewall-cmd --reload
sudo firewall-cmd --list-services

What this does: permits the DNS service through firewalld permanently, reloads the firewall, then lists allowed services.

Create your zone and NS

• Add a zone stanza for your domain in named’s configuration and a zone file with SOA, NS, A/AAAA, MX and other records.
• Publish at least two NS records in the zone that match the private nameservers you will register, for example ns1.yourdomain.tld and ns2.yourdomain.tld.
• Point those hostnames to real public IPs with A and AAAA records in the zone.

After BIND answers authoritatively for your domain and the private nameserver hostnames resolve, register the child nameservers (glue) at your registrar by mapping ns1.yourdomain.tld and ns2.yourdomain.tld to their IPs. Only then change the domain’s nameservers to those hostnames.

Troubleshooting common issues

• The registrar still shows the old nameservers: ensure you completed every confirmation step in their panel. Try again and wait a few minutes, then run whois.
• Pending change that never completes: verify you used the exact nameservers assigned by the destination. Some providers require a specific pair. Typos keep the domain pending.
• Domain fails with SERVFAIL: check for a stale DS record at the registrar. Remove it or update it to match the new signed zone.
• Intermittent resolution: check for NS mismatches between the parent and your zone, or across your nameservers. Make them consistent.
• Nothing resolves after switching to private nameservers: check that glue exists at the registrar and that your DNS server is reachable on UDP and TCP 53.
• Website is up but email is down: confirm MX, SPF and DKIM exist in the new zone and point to the correct mail service.

If you get stuck at any point, please open a support ticket. Tell us your domain and where you want to host DNS. We will help you check delegation and records.

What next

• If you have pointed your domain to Hostworld cPanel, add and manage DNS records in Zone Editor. For an introduction to server-side tasks, see our VPS guides.
• Looking for a performant UK VPS to host your own DNS or applications? See our Linux VPS page.
• If you plan to host email with us, make sure your MX, SPF, DKIM and DMARC records match your chosen mail service. We can review them in a ticket.