Separate registration from hosting
Keep the domain holder's registrar access and renewal route in place while changing only the authorised web hosting path.
Website hosting, authoritative DNS and domain registration may sit with different organisations. A web-file move does not transfer the registration. Before cutover, confirm the registrar login, legal holder, renewal contact and people authorised to change DNS.
Novasean hosting and domain registration are separate services unless your actual order says otherwise. Do not infer a bundled domain, a new registrar or a transfer from a web-host change.
Check custody from trusted records
Sign in through the registrar route you already know and compare the domain name, contact details, renewal setting and registration status with your order and invoices. If you do not know the registrar, use the domain’s registration data and past billing records to identify the right party, then verify through the registrar’s own site. Confirm who receives renewal notices and who can obtain transfer authorisation, but do not share an Auth-Code simply to move a website.
Record the current nameservers and DNS provider separately. The party that hosts the site may not operate the authoritative DNS zone, and a DNS change can affect mail and other services if the wrong zone is edited.
Keep the holder's registrar access
Have the domain holder retain a working registrar login, recovery route and current contact address throughout the move. Give the web agency only the DNS or delegation access needed for the authorised cutover, where granular access exists. If the agency currently owns the registrar account on the client’s behalf, resolve account and registrant authority in writing before changing hosts; a website export is not a domain handover.
For a web-only move, record the existing mail and other DNS dependencies before changing A or AAAA records. The related guide covers those technical record edits. If a registrar transfer is also intended, use the separate transfer procedure and protect renewal timing.
Confirm control after cutover
After the website responds from the new host, check the registrar account again. Verify the domain still appears under the expected holder, the renewal date and payment route remain understood, the nameservers are the planned ones, and the responsible person can request help. Save the before-and-after custody record. If the account is inaccessible or holder details are disputed, stop further DNS or transfer actions and contact the registrar and contracting parties through known channels.
An effective handover leaves the domain visible in the holder's registrar account, renewals assigned to a known payer and the new website serving at the intended names.
Frequently asked questions
Will cancelling old hosting cancel my domain? They are separate services, but check the actual orders and billing arrangements before cancelling anything.
Do I need an Auth-Code to point a domain at a new host? No. An Auth-Code belongs to a registrar transfer, not an ordinary DNS change.
Does possession of website files prove domain ownership? No. Confirm registrant and account control with the registrar.
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.