Skip to content

Knowledgebase

Change a 123 Reg domain to your assigned Nabtech nameservers

domains-dns

Use the Nameservers controls in your 123 Reg Domain Portfolio to point a registered domain at our assigned DNS service. This changes where its authoritative records are managed.

01 Prepare the destination

Obtain the exact nameservers for the relevant Nabtech service. Export or record the current DNS, then prepare the new zone with website, mail, verification and subdomain records. Check DNSSEC and parent DS requirements before moving to a differently signed service.

Review the domain's current status. 123 Reg's instructions require the domain to be eligible for the change, including its applicable lock setting. Resolve restrictions through the registrar's supported process rather than changing unrelated account details.

02 Update the nameservers

  1. Sign in to the 123 Reg Control Panel.
  2. On My Products, find the domain under Domains and select Manage.
  3. In Domain Portfolio, open DNS > Nameservers.
  4. Select Change Nameservers.
  5. Choose I'll use my own nameservers, enter the assigned hostnames and select Save.

Use the full intended list. Do not mix an old 123 Reg nameserver with an unrelated new server unless both are deliberately configured to serve the same zone.

03 Verify the transition

Check the saved list and public parent delegation. Query the Nabtech authorities directly to confirm the zone is present and consistent. The DNS Manager's record view and a recursive resolver's cached answer can temporarily differ.

Test website and mail separately. A nameserver change does not migrate website files, create destination mailboxes or copy every DNS record. Keep the old DNS and any required old hosting services until the migration checks are complete.

Why does my 123 Reg domain still show the old DNS result?

If the update is refused, read the registrar's error and verify hostname validity and domain status. If the update succeeds but the domain fails publicly, inspect missing destination records and DNSSEC first.

For a rollback, restore a reviewed working delegation and keep both sides' records available through cache overlap. Repeatedly switching without checking authoritative data can make the incident harder to diagnose. Give support the domain, time of change and relevant service reference.

Sources and further reading

Was this answer helpful?

Need a little more help?

Our support team can help you find the next step.

Contact support