THE SNAPREBUILD GUIDE · Website planning

How to connect a domain to a website safely

Follow a clear domain setup plan. Find the right accounts, use your website host's records and check your site and email before calling the job done.

Learning how to connect a domain to a website starts with knowing which service controls each part. Your domain seller, website host and email provider may be different companies. A website change should not accidentally disconnect your business email.

Use the exact setup details from your website host. There is no single address or record that works for every platform. This guide helps you plan the change and check the result.

The short answer

  • Find your registrar, active DNS host, website host and email provider first.
  • Save the current records and use only the new values supplied by your host.
  • Check both domain versions, HTTPS, key pages and email after the change.

How this guide was made

This guide uses Cloudflare documentation for DNS fields and mail records. The change log is a planning example, not a set of values to copy. No custom domain was connected or tested for this article. Your own host must supply the required records and connection steps.

Sources checked .

Know the four parts of the setup

Your domain is the name visitors type, such as example.com. Several services work together to make that name reach your site. They may be sold by one company or held in separate accounts.

Registrar and DNS host

The registrar manages your domain registration and renewal. The DNS host holds the records that point the name to your services. These are not always the same company.

Check which nameservers the domain uses to find its active DNS provider. Editing records in an old, unused account will not change where visitors go. Ask your provider if the two accounts are unclear.

Website and email host

The website host serves your pages. The email provider runs mail for your domain. Moving the website does not mean you want to move email too.

Confirm that you can access each needed account before launch. Store passwords in a password manager, not in the handoff sheet.

Back to contents

Make a domain handoff sheet

Use this sheet to record who manages each part. Keep passwords and recovery codes in a secure password manager, not in a shared planning sheet. The name example.com here is only an example.

Check the renewal date and recovery contact for the domain. If a former staff member owns the only login, resolve access before launch day. A clear owner makes both setup and future renewals easier.

Make a domain handoff sheet
ItemWhat to record
RegistrarCompany and person with account access
DNS hostWhere current records are managed
Website hostPlatform and exact domain setup instructions
Email providerMail service and current required records
Public addressWhether example.com or www.example.com is preferred
OwnerPerson who will make and verify changes

Back to contents

Get the records from your website host

Start with the domain setup page at your website host. It may ask you to add the domain before it gives you records. Copy the type, name and target exactly. Do not use values from a guide for a different platform.

An A or AAAA record points to an address. A CNAME points one name to another. Each record also has a TTL, which tells a cache how long it may keep that answer. Cloudflare documents these fields. Use the setting your host asks for.

Bracketed values are placeholders for your change log. They are not valid setup instructions to paste into DNS.

Get the records from your website host
BeforeChange to recordCheck afterwards
Save the current record for [website name]Type [host supplied type], target [host supplied value]Target matches the host instructions
Save the current record for [www name]Use the host supplied www settingBoth public versions reach the correct site
Save the current TTLUse the setting in the connection instructionsChange time and TTL are written down
List mail and verification recordsLeave them unless a planned change requires itMail and other connected services still work

Source for this section: [1] Cloudflare guide to managing DNS records

Back to contents

Save the current setup before changing it

Export the current records or save a clear copy. Include record names, types, values and TTLs. Note who will make the change and when. Keep this copy even after the new site works.

Mail uses provider records such as MX and authentication records. Cloudflare explains their roles. Preserve the entries your email provider requires, including relevant TXT or CNAME records.

If the host asks for a website record change, edit only the named records. If it asks for new nameservers, pause to plan the wider move. Nameservers decide which provider answers for the domain. The new DNS host needs the full required website, mail and verification setup before that switch.

Source for this section: [2] Cloudflare guide to domain email records

Back to contents

Check the site after the change

DNS caches and platform checks can take time to update. There is no fixed wait that proves every visitor is using the new destination. Watch the status in your website host and test the public address.

Check both the plain domain and the www version. Choose one as the main public address and confirm the other leads there as intended. Your host may manage this for you, but you still need to check the result.

Open the site with HTTPS, which protects the connection between the browser and the site. Confirm that the secure connection works and the expected pages load. Test the homepage, a service page and the contact path.

Back to contents

Use the symptom to guide the next check

Use the symptom and your change log to narrow the problem. Avoid making several new changes at once. It becomes harder to know which one helped.

The wrong website appears

Compare the active DNS record with the exact host target. Then check that the domain is attached to the correct project at the website host. Test the plain and www versions separately.

Record the result and time. Cached answers can differ for a while, so one successful browser check is not proof that every visitor has the new answer.

The browser shows an HTTPS warning

Check the domain and certificate status with the website host. Make sure the certificate covers the address you are opening. Do not ask customers to bypass the warning.

A page opening over plain HTTP does not settle this check. Verify the intended HTTPS address and its key links.

Email stops working

Compare the current mail records with your saved copy and the email provider instructions. If nameservers changed, check the records at the new DNS host.

Give the provider the change time and symptoms. Do not delete unrelated entries in an attempt to fix the problem.

Back to contents

Recover a failed change safely

Write down what failed, the last working time and each setting changed. Ask the responsible host to compare the old and new values. A wrong project attachment needs a different fix from a missing DNS record.

Restore a known prior setting only when the provider confirms it is the right recovery step. The old website or service must still be available. Restoring records that pointed to a closed account will not help.

After recovery, check website pages, HTTPS and mail again. Keep the failed change in your notes so the next attempt starts with evidence.

Back to contents

Finish with a real test

Send and receive a test email using accounts you control. Submit a labeled website inquiry and confirm it arrives. Check any important redirects from the old site if this connection is part of a move.

Record the final settings, checks and any open issues. Keep the old setup information until the change is stable. A domain connection is finished when the site and its related services work, not just when a dashboard shows a green mark.

Back to contents

Sources and further reading

Numbered links beside each section point to the source used there. Our examples and checklists are guidance from SnapRebuild. They are not claims of test results. Product details can change.

  1. Cloudflare guide to managing DNS records
  2. Cloudflare guide to domain email records
About the publisher

SnapRebuild sells a website building service. These guides are published under our editorial team name and use AI for research and writing. This is not a claim of independent expert review. Read how we make and update our content. Found an error? Tell us.

PUT YOUR PLAN INTO PRACTICE

Ready for a fresh start?

Bring your website or your business idea. Explore a SnapRebuild preview and decide what comes next.

Try your free preview