A website launch can fail even when the new site works perfectly on a preview address. The domain, DNS and hosting accounts connect visitors to the release, and those same records may also support business email and other services.
Related service: Website and ecommerce development- 01Confirm account access
- 02Inventory existing records
- 03Approve the exact changes
- 04Switch and verify public behavior
- 05Document ownership and rollback
SECTION 01
Ask the agency for an account and record map
Identify who controls domain registration, authoritative DNS and hosting, and who can approve changes. The business should retain appropriate ownership and recovery access. Inventory the records currently supporting the website, email, subdomains and verification services. A request to 'point the domain' is too vague when nobody has established which records will change and which must remain intact.
MDN explains how domain names resolve through DNS, and Cloudflare's record documentation illustrates record types and time-to-live settings. The exact controls depend on your provider. Ask the agency to record the old values, intended new values and reason for each change. A nameserver change affects a broader set of responsibilities than editing a single website record, so treat those actions differently.
SECTION 02
Illustrative example: moving a consultancy's brochure site
Imagine a consultancy moving its public website while keeping its existing business email provider. The new site passes preview checks, but the launch brief also preserves mail-related records and a separate client-portal subdomain. The agency verifies the root and www hostnames, HTTPS certificates and the preferred-domain redirect. It does not assume that one working browser tab proves every hostname is correct.
The business agrees a launch window and identifies who can restore the previous website record if needed. Because DNS responses can be cached, different visitors may temporarily reach different destinations. Both environments need a deliberate plan for forms during that transition. The first release can keep the change narrow rather than combining a hosting move, registrar transfer and email migration unnecessarily.
SECTION 03
Accept the domain, email boundaries and recovery access
Test public DNS resolution, HTTPS, the homepage, a deep link and the lead form through the intended domain. Confirm that unrelated mail and service records remain as approved, involving their owners for functional checks. Verify from more than one network or resolver where practical. Record what was checked and distinguish a configuration check from actual email delivery or application testing.
Handoff should provide an account inventory, renewal owner, record-change log and recovery instructions stored securely. Do not place passwords in a public document or leave a single agency employee as the only recovery contact. A managed hosting setup can simplify maintenance, but it does not remove ownership questions. Agree ongoing responsibility for domain renewal, certificate issues and future DNS changes before closing the launch.
SECTION 04
Frequently asked questions
Is the domain registrar always the DNS provider?
No. Registration, authoritative DNS and hosting can be managed by different organizations and require separate access.
Will changing website hosting move our email too?
Not necessarily. Preserve the approved email records and avoid combining unrelated migrations without a separate plan and verification.
Why can people see different versions after a DNS change?
Resolvers and devices may cache previous DNS answers. Plan the transition and verify the new configuration without assuming instant universal updates.
PRIMARY REFERENCES
Sources and further reading
These references cover the standards, platforms, or published prices discussed in the guide. Worked examples and checklists are our editorial guidance.
EDITORIAL METHOD
About this guide
We use AI to assist with drafting and editing. Catapult AI Work is responsible for the published content. Examples illustrate possible approaches; they are not client case studies unless identified as such.
Budget examples are not Catapult package prices. Check linked provider pages for current fees and plan limits before making a purchase.
Read the editorial policy