Websites & Infrastructure

Domain & DNS Services

Make the routing behind your business domain easier to understand and manage. We help set up or troubleshoot the domain and DNS records that direct visitors and email toward the services you use.

A conceptual workspace with a website on desktop and laptop screens, a server cabinet, and network cabling.
Websites & Infrastructure, illustrated.

START WITH THE BUSINESS

Know which account controls which part.

A domain registration, DNS provider, website host, and email service may be separate accounts. Understanding that division is essential when a website moves or a record needs changing.

  • You are unsure where your domain's DNS records are managed.
  • A website launch or hosting move needs coordinated domain changes.
  • Website or email routing needs investigation across several providers.

Clarify the routing before changing records.

The work starts with the existing providers, ownership, and intended destination. We review relevant records and agree the changes so unrelated services and responsibilities remain visible.

Map domain responsibilities.

Identify the registrar, DNS host, website destination, and relevant email provider. Document which party or account controls the changes needed for your request.

Set up the agreed records.

Prepare or update the DNS records required by the selected website or email services. Review existing dependencies and distinguish the requested change from unrelated records.

Troubleshoot and verify routing.

Check the relevant DNS answers and service destinations, then document what was observed. Coordinate with the responsible hosting or email provider when the issue extends beyond DNS.

ILLUSTRATIVE EXAMPLE

Moving a website while keeping business email.

Consider a business changing its website host while email remains with the current provider. We would identify who controls DNS, review the website and mail-related records, and agree which destination should change. Verification would check the agreed website routing and preserve the documented mail dependencies. The scope would also clarify who is responsible for the website and email services themselves.

Make a focused change with context.

  1. Identify the accounts and goal.

    Discuss the domain, existing services, and desired change. Confirm who owns the accounts and who can authorize the relevant record updates.

  2. Review the records.

    Check the current routing, provider instructions, and related dependencies. Agree the exact change and how the intended destination will be verified.

  3. Change and document.

    Apply or guide the agreed updates, review the resulting DNS answers, and record the responsibilities needed to manage the domain afterward.

Questions about domains and DNS.

Do you need to own our domain account?

Your business should retain clear ownership of its domain. We agree an appropriate access or guided-change arrangement for the work and document who is responsible for ongoing account management.

Does changing DNS move our email messages?

DNS directs traffic toward a service; it does not copy mailbox contents. If the request includes changing email providers or moving data, that requires a separately agreed plan with the relevant services.

A CLEAR NEXT STEP

Tell us the domain and the intended change.

Describe the website or routing issue and which providers you currently use. We can help identify the accounts and records involved.