Point each reseller customer domain to the nameservers assigned to the reseller service and verify the zone before changing delegation.
Every customer SiteWorx account needs a matching DNS zone, correct domain delegation and valid records for its website and email. Create and check the customer account before changing a live domain’s nameservers.
Before you start
- Sign in to NodeWorx using the reseller account.
- Identify the customer SiteWorx account and confirm the domain has been added to it.
- Copy the exact nameservers shown in the reseller service welcome details. Standard services normally use ns1.tudornet.uk and ns2.tudornet.uk, but the service details are the source of truth.
- Record the domain’s current nameservers, DNS records and TTL values.
- Check whether the registrar currently publishes a DNSSEC DS record. The standard InterWorx nameservers are not DNSSEC-signed, so any stale DS record must be removed before switching to them.
Use the assigned Tudor Internet nameservers
- Create the customer SiteWorx account and confirm the domain appears in its DNS zone.
- Check the A or AAAA records for the website and the MX, SPF, DKIM and DMARC records required for email.
- At the domain registrar, replace the current nameservers with the exact pair assigned to the reseller service.
- Save the change and check the registry or registrar now returns the intended NS records.
- Allow the previous DNS TTL and registrar caching to expire. Do not repeatedly change the delegation while propagation is in progress.
- Query each authoritative nameserver directly and confirm they return the same zone serial and records.
- Test the website over HTTPS and send email to and from an unrelated external mailbox.
Use external DNS instead
- Keep the registrar’s existing nameservers or move the domain to the selected external DNS provider.
- Create the website A/AAAA records using the address assigned to the SiteWorx account.
- Create all required MX and TXT records for hosted email.
- Issue or renew the SSL certificate only after the public DNS records point to the hosting service.
- Retest the website and email after the previous TTL expires.
Private nameservers
Do not publish names such as ns1.customer-domain.example until Tudor Internet has assigned the service and the registrar has registered the required child nameserver or glue records. Follow the separate private-nameserver guide and keep the underlying Tudor Internet nameservers available during the transition.
Confirm the result
- The registry lists the intended nameservers.
- Every authoritative nameserver returns the same A, AAAA, MX and TXT records.
- The website loads over HTTPS without a certificate-name error.
- Hosted email can send and receive externally.
- No stale DS record causes DNSSEC validation failures.
Common problems
| Symptom | Likely cause | What to do |
|---|---|---|
| Some networks show the old website | The previous TTL or resolver cache has not expired. | Check the authoritative nameservers first and wait for the old TTL before making another change. |
| The domain returns NXDOMAIN | The domain is delegated but the zone is missing from the customer SiteWorx account. | Create or restore the zone on every assigned nameserver before retrying. |
| The domain returns SERVFAIL | A stale DNSSEC DS record exists, nameservers disagree, or an authoritative server is unavailable. | Check the parent DS and direct authoritative answers. Remove a stale DS through the registrar before using unsigned nameservers. |
| The website works but email does not | MX, SPF, DKIM or mail-host records were not copied to the active DNS provider. | Compare the active zone with the SiteWorx email configuration and add the missing records. |
When to contact Tudor Internet
Open a support ticket if the assigned nameservers do not contain the customer zone, if private nameservers need to be provisioned, or if the authoritative servers return different answers. Include the reseller service, customer domain, registrar, current nameservers, intended nameservers and exact error.
Related articles
- Plan private nameservers for reseller customers
- Troubleshoot SSL for a reseller customer domain
- DNSSEC availability and changes
- Use included SiteLock Lite and 360 Monitoring Lite on reseller hosting
Last reviewed: 2026-07-25.
