You paid about twelve dollars, got a confirmation email, and now you own the name. Then you opened the registrar’s control panel to look at what you bought and found words like nameservers, A record, and MX. Nothing you clicked made a website appear.
The distance between owning a name and having it point at something is one settings change. It feels bigger than that because of the worry sitting underneath it: if people already email you at that address, you don’t want to touch anything that might stop the messages.
The domain and the website are two purchases
The domain is the name. The website host is the machine that answers when someone types the name. You rent the name from a registrar for roughly $10 to $15 a year for a .com, and you pay a host separately to serve the pages. Different companies, different jobs. Nothing requires them to be the same one.
Keeping them apart is the safer arrangement. A domain registered in your name, in your own account, on your own card, is the one piece of your web presence nobody else holds. Decide in two years that you want a different website and you point the name somewhere new. If the name lives inside your website provider’s account, moving means an unlock and a transfer request at exactly the moment you’re least happy with them.
Worth saying plainly, since we’re the ones writing this: AgentBuild doesn’t sell domains. You buy the name wherever you like, Namecheap, Cloudflare, GoDaddy, and connect it. We’d rather the asset sat in your account than ours.
What “connecting” means
Somewhere out there is a directory that answers one question: when someone types yourbusiness.com, which machine should reply? Connecting your domain means writing your website’s address into that directory. The entries are signposts. One says “the website is over here.” Another says “email goes over there.”
There are two ways to do it, and your host tells you which one it wants.
- Change the nameservers. This hands the whole directory to your host, signposts and all. They manage the entries from then on. Fewer things for you to type, and the setup is often a single field at your registrar.
- Leave the nameservers alone and add a record or two. Your host gives you the exact values; you paste them into the DNS section at your registrar. Only the signposts you touch change.
Neither is more advanced than the other. The difference is who holds the pen, which is why the next section exists.
Before you change anything, answer the email question
If you already receive mail at your domain, say so, out loud and in writing, to whoever is helping you, before a single setting moves. Mail signposts live in the same directory as website signposts. Handing that directory to a new provider without carrying the mail entries across is how a dental office stops receiving appointment requests on a Tuesday and doesn’t notice until Thursday.
Done properly, connecting a website leaves your email exactly where it was. Two ways to be sure:
- Keep the nameservers where they are and add only the website records. Your mail settings stay untouched because you never touched them.
- If you do move the nameservers, copy the existing mail records across to the new provider first. Ask for a screenshot or export of the current settings so you have something to compare against.
The sentence to say: “I already use this domain for email. Show me the current mail settings before we change anything, and confirm they’ll still be there afterward.” Then test it yourself. Send a message to your business address from your personal account and watch it arrive. Thirty seconds, and it’s the only proof that counts.
Nothing happens instantly, and that’s not a fault
Once you save the change, it spreads outward. Some visitors see the new site within minutes. Other people’s internet providers hold onto the old answer for a while, usually under an hour, sometimes a day or two. During that window it’s normal for the site to load for your sister across town and not for you.
The mistake here is impatience. Editing the setting again because nothing happened in ten minutes restarts the clock and muddies what you actually configured. Save once, check in an hour, go looking for a problem only if the next day still shows nothing. While you wait, open the address on your phone with wifi switched off: a different network often gets the newer answer first.
Getting hello@yourbusiness.com
A personal address on a business card costs you credibility, and fixing it is cheap. Two levels, and many owners never need the second.
- Forwarding. Mail sent to hello@yourbusiness.com lands in the inbox you already read. Many registrars include it at no extra cost. The catch is replies: unless you set up sending too, your answer goes out from your personal address.
- A real mailbox. A mail provider gives you an inbox you send and receive from, priced per person per month. Worth it once you’re answering customers all day, or once someone else needs their own address at the business.
What to ask for, rather than what to click: “I want hello@mybusiness.com to reach me. Given that I [reply to customers daily / just need a contact address], is forwarding enough or do I want a mailbox? Tell me which records to add and where.”
Either way, the provider will ask you to add a few records proving you’re allowed to send mail from your own domain. Add them. Skipping that step is a common reason a small business’s email quietly lands in spam.
None of this is knowledge you need to carry around. You use it once, on the day you connect the name, and then it sits there working. Once the name resolves, give the site one last check before you tell anyone. The part worth keeping is smaller: the domain is yours, it renews in your account, and it’s what keeps every other choice reversible.