What Happens When You Connect a Custom Domain

Connecting a domain feels like one action, but it is a chain of small handoffs between your registrar, your DNS host and your website host. When you know the order, a delay stops looking like a failure and starts looking like a stage that has not finished yet.

The chain in one view

Three parties are involved. The registrar is where you bought the name. The DNS host holds the records that say where the name points, and for many owners this is the same company as the registrar. The website host is where the pages actually live.

The sequence runs the same way almost every time:

1. You add one or two DNS records at your DNS host.
2. The records spread across the internet’s caches.
3. The website host notices the name now points at it and confirms ownership.
4. A security certificate is issued for the name.
5. The site starts answering on your domain over HTTPS.

Nothing in that list requires you to do anything after step one. Most of the waiting happens in steps two through four.

What the records actually say

A DNS record is a short instruction. An A record says “this name lives at this numeric address.” A CNAME record says “this name is an alias for that other name.” Your website host will tell you which records to create, and the values are specific to your account, so copy them exactly rather than retyping from memory.

The bare form of your domain, with nothing in front of it, usually takes an A record. The “www” form usually takes a CNAME. Many owners set up only one of the two and then wonder why the other shows an error page. Set up both, and let the host redirect one to the other.

A worked example

This is an invented setup, shown only as before and after wording. Example Bakery owns a domain through a registrar and has just chosen a website host.

Before: the domain points at the registrar’s parking page. Visitors see an advertisement for domain services.

Records to add at the DNS host: Type A, name “@”, value “the address your host gives you” Type CNAME, name “www”, value “the hostname your host gives you”

After: the domain points at the website host. The host shows “waiting for verification” until it can see both records.

Notice that the old parking records have to be removed or replaced. Two conflicting A records for the same name will send some visitors to the old place and some to the new one.

When it does not appear

Caches are the usual cause. Every resolver along the way remembers the old answer for a while, and that memory has its own timer, called the TTL. Waiting is a legitimate fix, and so is checking from a different network, such as your phone off Wi-Fi, which skips your home router’s cache.

If a full day has passed, check these in order: the record type matches what the host asked for, the name field is correct, there is no leftover record from the previous setup, and the nameservers at the registrar are the ones where you edited the records. That last one catches a surprising number of cases. You can edit records perfectly at a DNS host that the registrar is not pointing to, and nothing will change.

Common mistakes

• Editing records at one provider while the registrar still points at another provider’s nameservers.
• Leaving the old parking record in place next to the new one.
• Typing the value by hand and introducing a stray space or a missing character.
• Setting up the bare domain but not the “www” form, or the other way around.
• Changing records repeatedly during the wait, which restarts the confusion each time.

Try this today

1. Log in to your registrar and write down which nameservers the domain currently uses. That tells you where the records must be edited.
2. Look at the current records and delete any that point to a parking page or an old host before you add the new ones.
3. After adding the records, wait, then test the bare domain and the “www” form separately, once on Wi-Fi and once on mobile data.

Field notes

• Connecting a domain is a chain of handoffs, and most of the time goes to caches expiring.
• Copy record values exactly as your website host gives them.
• Remove old or conflicting records instead of stacking new ones on top.
• Confirm that the registrar’s nameservers match the place where you edit records.
• Test the bare domain and the “www” form separately.

Would you rather not build all of this by hand? websiites.com creates a complete website from a paragraph about your business, and you can see the finished site before you pay anything. The how it works page walks through the steps.

Related reading

• How It Works — See the full site before you pay.
• Frequently Asked Questions — Everything you need to know about websiites.com: pricing, how the AI build works, domain setup, cancellation, and what happens if you’re not happy.
• Website Builder Pricing — Simple, transparent pricing for your AI-built business website.