A domain can involve several providers even when you pay one company. Identify who controls registration, public DNS and hosting before requesting a change. This prevents an urgent renewal request being sent to a website developer who cannot renew the name.
IN THIS ARTICLE
01 Identify the roles
| Role | Responsibility | Useful evidence |
|---|---|---|
| Registry | Runs the relevant domain namespace and registration database. | The extension's official registry information. |
| Sponsoring registrar | Maintains the registration through the registry. | The registrar identified in authoritative registration data. |
| Reseller or account provider | Supplies the customer account, invoices and first support contact. | Your order, paid invoice and authenticated account. |
| DNS operator | Answers public queries for the delegated zone. | The authoritative nameservers and their actual answers. |
| Hosting or email operator | Runs the destination website or mail service. | Service details and the relevant address or MX records. |
02 Build a reliable contact record
- Sign in through your known Nabtech client-area address and locate the domain order. Record the domain, account owner and renewal arrangement.
- Use an authoritative RDAP lookup to identify the sponsoring registrar. A different upstream name can be normal for a reseller service.
- Check the live nameserver delegation. Find the DNS account that controls those servers instead of relying on whichever DNS editor is easiest to open.
- Record the website and email suppliers separately. A website move need not involve changing the registrar.
- Keep these details in your organisation's service inventory, with an authorised backup contact for each account.
Who should I contact when something breaks?
For invoices, renewals and transfer orders bought through us, start with the relevant Nabtech account and order reference. For incorrect public records, identify the authoritative DNS operator. For a website error with correct DNS, provide the hosting service details. If you are uncertain, share the domain and symptoms so the affected layer can be identified.
A public lookup does not prove who is entitled to access your customer account. Account recovery still requires ownership verification. Do not send passwords or transfer codes merely because someone claims to work for an upstream provider.