Keep domain ownership with the correct organisation and plan DNS, mail and renewal separately from the hosting approval.
Applies to: Approved Non-Profit & Club Hosting services
Approved organisations use the standard SiteWorx hosting tools and remain responsible for their content, users, renewals and security. Changes to the organisation may trigger a fresh eligibility review.
Before you start
- Sign in to the Customer Portal and open the approved hosting service.
- Take a current backup before changing website files, databases, DNS or application configuration.
Step-by-step
- Confirm the registrant name and administrative authority for the domain.
- Register, transfer or retain the domain with an appropriate registrar; discounted hosting does not itself prove domain ownership.
- Prepare the website and mailboxes before changing nameservers or records.
- Update DNS in a controlled window and verify website, HTTPS and external email delivery.
- Enable auto-renew or documented renewal responsibility for the domain.
- Ensure at least two current officers know where the domain is registered and how renewal notices are received.
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
- Domain registrant and account holder responsibilities
- Change a domain’s nameservers
- Plan a DNS change with minimal downtime
- Start using an approved Non-Profit Hosting service
- Renew Non-Profit & Club Hosting
Last reviewed: 2026-07-18.
