Skip to content

How to point a domain to a website

By Ash, Founder, HosteazePublished 2 min read

You have two options. Change your domain's nameservers to the ones your host gives you, which hands over all your DNS. Or keep your DNS where it is and add an A record for the root domain plus a CNAME for www. Either way, copy your email records first so your inbox keeps working.

Wooden arrow-shaped signpost against a blue sky, pointing the way
Credit: geralt via Pixabay

Buying a domain and building a website are two separate jobs, and pointing one at the other is the bit in the middle that nobody explains. It takes about ten minutes of clicking. The hard part is not breaking anything else on the way, mostly your email.

Which method should I use?

Change nameserversAdd an A record and CNAME
What it doesHands all your DNS to your new hostChanges only where the website points
Best forA fresh start, or when your host manages email tooKeeping DNS where it is, such as at Cloudflare or your registrar
Risk to emailHigh, unless you copy your records firstLow, email records aren't touched
How long to take effectUp to 24 to 48 hoursUsually under an hour

For most small businesses with email already working, adding records is the safer choice. If you're starting from scratch with nothing else on the domain, changing nameservers keeps everything in one place.

Before you start: copy your existing records

This step takes two minutes and is the difference between a smooth move and a week of missing emails.

Option 1: Change your nameservers

Option 2: Add an A record and a CNAME

Not sure which record does what? A record vs CNAME explains the difference.

How do I know it worked?

Check your domain's A record in the Dig tool. Once it shows your host's IP address, visit your site using mobile data rather than your home broadband, which might still have the old answer cached. Most changes appear within an hour; see how long DNS propagation takes if yours is slower.

Last of all, make sure the site loads with https://. Most hosts issue the SSL certificate automatically once the domain points at them, which can lag a little behind the DNS change.

Step by step

  1. 1.Find where your DNS is managed

    Look up your domain's nameservers with a free DNS lookup tool. They show which company currently answers for your domain.

  2. 2.Copy your existing DNS records

    Screenshot or export every record, especially MX, TXT and any CNAMEs for email, before changing anything.

  3. 3.Get the values from your host

    Your web host gives you either nameservers or an IP address and hostname to use.

  4. 4.Make the change

    Either replace the nameservers at your registrar, or add an A record on @ and a CNAME on www in your current DNS.

  5. 5.Check and wait

    Confirm the new values with a lookup tool, then allow up to 48 hours for every visitor to see the change.

Frequently asked questions

Should I change nameservers or just add an A record?

Change nameservers if you want your host to manage everything in one place. Add records if your DNS is somewhere you like, such as Cloudflare, or if your email depends on records you don't want to move.

Will pointing my domain to a new website affect my email?

Changing an A or CNAME record won't. Changing nameservers can, if your MX, SPF and DKIM records aren't copied to the new DNS provider first.

Do I need to transfer my domain to point it at a new host?

No. You can leave the domain registered where it is and only change where it points. Transferring is a separate, optional step.

Sources

  1. RFC 1034, Domain Names, Concepts and Facilities
  2. Cloudflare, DNS record types
  3. Google Admin Toolbox, Dig
Red octagonal stop sign against a blue sky, like a mail server refusing a messageQuestionWhat does a 550 email bounce error mean?A 550 error means the receiving mail server permanently refused your email, so it won't try again. The extra code after it gives the reason. 5.1.1 means the address doesn't exist, 5.7.1 means it was blocked as spam or by a policy, and 5.7.26 means your domain's SPF or DKIM authentication failed.Email and domains · 14 October 2026Two stacked cardboard boxes, ready for a move, like your email moving to a new providerTutorialHow to change MX records without losing emailLog in to wherever your domain's DNS is managed, delete the old MX records, and add the new ones your email provider gives you with the exact priority numbers. Lower the TTL a day before if you can. New email reaches the new provider within minutes to hours, so keep the old mailboxes open for a few days.Email and domains · 14 October 2026Yellow wooden signposts pointing in different directions on a mountain pathQuestionA record vs CNAME, what's the difference?An A record points a domain name straight at an IP address, such as 203.0.113.10. A CNAME points a name at another name, which then supplies the address. Use an A record for your root domain and a CNAME for subdomains like www when your host gives you a hostname. A CNAME can't sit on the root domain.Email and domains · 13 October 2026The Earth from space covered in a web of glowing network connections, showing how DNS answers spread worldwideQuestionHow long does DNS propagation take?Most DNS changes are visible within a few minutes to an hour, but some take up to 48 hours. The wait depends on the record's TTL, which tells servers how long to keep the old answer, and on whether you changed a record or your nameservers. Nameserver changes are usually the slowest.Email and domains · 13 October 2026Tangled mess of electrical cables on a telegraph pole against a blue skyQuestionHow do I fix "SPF record too many DNS lookups"?SPF allows a maximum of 10 DNS lookups. Every include, a, mx, ptr, exists and redirect term counts, including the ones hidden inside each include. Go over and SPF returns a permanent error, so it fails for all your email. Fix it by removing services you no longer use and dropping unnecessary a and mx terms.Email and domains · 13 October 2026

Want email on your own domain?

Hosteaze hosting plans let you set up mailboxes on your own domain. See what each plan includes.

See hosting plans