Choose Custom DNS at Namecheap when your domain should use the nameservers assigned by Nabtech. Namecheap's BasicDNS and Web Hosting DNS choices point to different Namecheap services, so use the option that matches your actual destination.
IN THIS ARTICLE
01 Prepare the new zone
Find the exact Nabtech nameservers in the relevant service details. Prepare the destination zone with all website, email, subdomain and verification records before the switch. Save a copy of the old zone and check DNSSEC requirements.
If you use Google Workspace, Zoho, OX App Suite or another external mail provider, retain its current records. Moving registrar delegation does not create those records in the new service.
02 Change Namecheap's setting
- Sign in to Namecheap.
- Open Domain List and choose Manage beside the domain.
- Find the Nameservers section.
- Select Custom DNS and enter the assigned nameserver hostnames.
- Save with the green checkmark and confirm the resulting list.
Enter names such as ns1.example.net. If the provider supplied names and IP addresses, the custom-nameserver fields take the hostnames. Registering personal nameserver glue is a separate task.
03 Edit records in the correct place
Once the new service is authoritative, edit the domain's records in that service. Namecheap's Advanced DNS controls may no longer manage the active zone. This is expected when using another provider's nameservers.
In Nabtech DNS Manager, check the exact domain and entitlement before editing. An administrator's view and a customer's allowed controls may differ.
04 Verify website and email
Inspect parent delegation and query each new authority directly. Check A and AAAA records as well as www. Send and receive test email using the intended mail service.
Allow for cached old answers and keep the former DNS service available during the transition. Do not assume a fixed number of hours guarantees every resolver has refreshed.
What should I check when Namecheap Custom DNS does not work as expected?
For a Namecheap validation error, check the complete nameserver list and the extension's requirements. For SERVFAIL after the change, inspect the parent DS and signing chain. For a working website but failed email, compare MX and related mail records with the provider's exact instructions.
Check the apex and www names separately and compare IPv4 with IPv6. A correct A record can coexist with a stale AAAA record that sends some visitors to the previous host. Keep both providers' record inventories while investigating.