Buying a domain is the easy part. Making it load your site is where most beginners get stuck, usually because two changes are made at once: the domain is pointed at new hosting, and DNS is moved to a new provider. Split those tasks and the process becomes predictable.

Two ways to point a domain

You can hand DNS control to your host by changing nameservers, or you can keep DNS where it is and add records that point to your server. Both work. They fail in different ways.

Option A: change the nameservers

Your hosting control panel lists two or more nameservers, for example ns1 and ns2 followed by a provider domain. Copy them exactly, log in at your registrar, and replace the existing nameservers with those values. The host now manages every DNS record for the domain.

This is the simplest option for a new site with no other services attached. It is also the riskiest if you already use the domain for something else, because changing nameservers moves mail records too. If your email lives at the registrar or a separate provider, either recreate the MX, SPF, DKIM, and DMARC records in the new DNS zone or use Option B.

Option B: keep DNS and add A records

Leave the nameservers alone. At the DNS provider, create an A record for the root domain (@) pointing to the server IP shown in your control panel, and a CNAME for www pointing to the root domain or an A record with the same IP. Mail records stay untouched, which is why this is the safer choice for domains with active email. The goal is a site that loads for visitors and keeps any existing services running.

Some registrars call the root record @ and others call it blank or the domain name itself. The meaning is the same. If the provider offers a proxy or CDN toggle, turn it off until the site loads correctly over HTTPS, then enable it if you want it.

How long propagation really takes

DNS changes are not instant because resolvers cache answers for the record's TTL. A TTL of 3600 means one hour, but some networks keep older answers longer. Most changes appear within a few hours; allow up to 48 hours before assuming something is broken.

Check progress with a public DNS lookup tool or the nslookup and dig commands. Query both the root domain and www. If your own computer still shows the old site after public resolvers show the new one, flush the local DNS cache or test from a phone on mobile data. Do not keep changing records every ten minutes; that resets the clock and makes the result harder to read.

Common mistakes that break the launch

  • Typing the nameservers with a missing dot, an extra space, or the wrong number.
  • Pointing the root domain but forgetting www, so half your links fail.
  • Leaving an old AAAA record that sends IPv6 visitors to the previous server.
  • Moving nameservers without recreating MX records, which silently stops email delivery.
  • Requesting SSL before DNS resolves, then forcing HTTPS and creating a redirect loop.
  • Testing once, seeing the old page, and undoing a change that was still propagating.

Keep email working

If mail is handled outside this hosting account, treat DNS records as a package. Before any change, export or screenshot the current MX, SPF, DKIM, and DMARC entries. After the change, compare them field by field. Send a test message from an outside address and reply to it. If you cannot find a record, ask the mail provider for the exact values before changing nameservers. A site that loads but cannot receive mail is a worse outcome than a site that loads a day late.

Launch checklist

  1. Confirm the hosting account is active and the site loads through the temporary URL.
  2. Copy the nameservers or server IP from the control panel.
  3. Decide whether DNS stays at the registrar or moves to the host.
  4. Make the change at the registrar and save the settings.
  5. Wait, then verify the root domain and www with a public lookup.
  6. Request free SSL once DNS resolves, and confirm the certificate covers both names.
  7. Force HTTPS only after the certificate is active.
  8. Test the site on mobile data, send a test email, and update the WordPress site URL if needed.

If a step fails, change one thing at a time and recheck. The FAQ covers the most common DNS and SSL questions, and the guide to creating your hosting account explains where to find the nameservers and server IP. If you do not have hosting yet, register a free account first, then work through this checklist before you publish the first post.