Use the exact DNS records supplied by the destination and preserve unrelated email records.
Applies to: Websites, domains and document roots in SiteWorx
Each website must have the correct domain assignment, document root, DNS destination and certificate. Treat changes to a live primary domain or document root as production changes and take a backup first.
Before you start
- Sign in to the Customer Portal and open the affected hosting service.
- Take a current backup before changing website files, databases, DNS or application configuration.
Step-by-step
- Obtain the required A, AAAA, CNAME or nameserver values.
- Back up the current DNS zone.
- Apply the records at the authoritative DNS provider.
- Wait for the previous TTL.
- Verify root, www, HTTPS and email separately.
Confirm the result
- The intended hostname loads over HTTPS from a private browser session and serves the correct website.
- Forms, database-driven pages and the administration area work without a new PHP, permission or redirect error.
Common problems
| Symptom | Likely cause | What to do |
|---|---|---|
| Some networks show the new result while others show the old one. | Recursive DNS caches have not expired or authoritative nameservers do not return consistent data. | Check the authoritative answer first, compare all listed nameservers and wait for the previous TTL before making another change. |
| The domain returns NXDOMAIN or SERVFAIL. | The zone is missing, delegation is wrong, DNSSEC is broken or an authoritative server is not responding. | Verify delegation at the registry, confirm the zone exists on every authoritative server and remove stale DS records only through a controlled DNSSEC rollback. |
When to contact Tudor Internet
Open a ticket through the Customer Portal when the checks above do not resolve the issue, when an action is unavailable for your service, or when continuing could risk data loss or service interruption. Include the following so the request can be investigated efficiently:
- The affected domain and SiteWorx account
- The exact error text and time
- The last change made
- Relevant log lines with passwords and personal data removed
Do not send passwords, private keys, full payment-card details, one-time authentication codes or unredacted identity documents in an ordinary support reply.
Related articles
- Add another website or domain in SiteWorx
- Secondary domains, pointers and subdomains
- Find a website document root
- Redirect a website from HTTP to HTTPS
- Create custom 404 and other error pages
Last reviewed: 2026-07-18.
