Find nameserver controls
To change a web address record, locate authoritative DNS first. Change registrar nameservers only after preparing the full new zone.
Nameservers choose the authoritative DNS provider; a record edit changes data there. Moving a website often needs only a web-record update. Registrar-side nameserver controls vary with domain status, registrar integration, provider configuration and permissions.
Before touching anything, identify the exact registered domain and the intended DNS provider. A mistake in the nameserver set can interrupt all records, including email. Use the full-zone migration guide before making a delegation change.
Locate the correct domain record
Sign in to the verified client portal and look for Domains or My Domains if available. Open the exact domain, not a hosting service with a similar name. Read the current status, registrar or provider information shown, and existing nameserver set. If a Nameservers or Manage Nameservers action appears, record the present values before editing. WHMCS stores nameserver fields for managed domain records, but its administrator documentation does not guarantee every customer has a working self-service registrar action.
If the domain is not listed, it may be registered with another provider, under another client account or outside this portal. Check your registration receipt or registrar account. Do not add a new registration order for an already registered name just to reach settings.
Choose the right control for the task
For an A, AAAA, MX or TXT change, first find the domain’s current authoritative DNS provider; a WHMCS domain record is not necessarily its DNS editor. If the task genuinely requires moving authority, prepare the complete new zone and DNSSEC sequence, then obtain the exact new nameserver hostnames from that provider. Do not paste an IP address into a nameserver hostname field or replace only one name in a provider-required set.
If nameserver controls are absent, greyed out or reject the update, ask the registrar or hosting provider which account can submit the delegation change. A transfer lock or registrar verification may also affect a requested operation; do not infer the cause from a generic UI error. Do not ask support to change NS until the new zone has been verified.
Check actual delegation after an authorised change
Once an authorised change is made, confirm the registrar accepted the intended set and query the parent delegation, for example dig example.com NS +trace. Query each delegated nameserver directly for representative A, MX and TXT answers. Caches can retain the old delegation for its TTL, so keep old and new zones available and consistent during the overlap. Test website and mail separately. A new panel value alone does not prove the public delegation or records have changed.
If the wrong set was submitted, contact the registrar promptly and restore the saved set according to its process while checking both zones and DNSSEC state. Do not keep toggling values to chase cached responses. Share exact nameserver hostnames and timestamps with support, but no login credentials.
Illustrative result: the panel shows the new nameservers, but parent delegation still lists the old set. Keep both zones working and recheck the registrar and parent rather than changing records repeatedly.
An apparently correct new zone may still fail if DNSSEC delegation remains tied to old keys; include DNSSEC in the rollback check.
Common questions
Where do I change one A record? At the actual authoritative DNS provider, not necessarily in the domain’s nameserver screen.
Why is there no Nameservers button? The domain, registrar integration or your account permissions may not provide self-service changes.
Will nameserver changes preserve email? Only if the new authoritative zone has the required mail records and dependencies.
Sources and technical references
Related guides
Was this guide helpful?
If you accepted optional analytics, your Yes/No answer and this guide’s page address are sent to Google Analytics. No written feedback is collected. Read our privacy statement or change your choice in .
Need help with your service?
Open your client area or contact Novasean. Describe the symptom and checks you have performed. Keep passwords, recovery codes and private keys out of your message.