Connecting a domain to your website is the step that trips up more people than any other, and it is almost always simpler than it looks. This guide explains, in plain English, what a domain is, where its settings live, and exactly what to click to point it at your site. No prior experience with a registrar dashboard required. Once your records are set, the work is done; the rest is just waiting.
What a Domain Actually Is
Your domain (for example, smithlawomaha.com) is your address, not your building. The building is your website: the pages, the words, the photos, all of it sitting on a server somewhere. The domain is the sign out front that tells a visitor's browser where to go.
These two things are usually bought from two different companies, and that is the source of nearly all the confusion. You buy the domain from a registrar (GoDaddy, Namecheap, Google Domains, and so on). Your site lives with a host (in your case, SmashWebs). Connecting a domain just means telling the registrar, "when someone types my address, send them to my house." You do that by editing a few DNS records.
DNS stands for Domain Name System. Think of it as the internet's phone book: it turns a name a human can remember into the numeric address of the server your site runs on. You do not need to understand how the phone book is printed. You just need to add two lines to your listing.
Where Your DNS Lives (and How to Find It)
Your DNS settings live wherever you bought your domain. Not where your site is hosted, not in your email, not on your computer. If you paid for the domain, whoever charged you is your registrar, and that is where you are headed.
Log in to that company's website and look for a menu item named DNS, DNS Settings, DNS Records, or sometimes Advanced DNS. It is usually one or two clicks from your list of domains. Here is where it hides at the common registrars:
- GoDaddy: My Products, then DNS next to your domain.
- Namecheap: Domain List, Manage, then the Advanced DNS tab.
- Cloudflare: select your domain, then DNS, then Records.
- Squarespace / Google Domains: Settings, then Domains, then DNS Settings.
Pointing Your Domain, Step by Step
You will add two records: one for the plain version of your address (smithlawomaha.com, called the apex or root) and one for the www version (www.smithlawomaha.com). You want both, because clients type both. SmashWebs shows you the exact values to paste, with a copy button for each, so you never have to type them by hand.
In your SmashWebs dashboard, open Domain from the sidebar and enter the domain you own. SmashWebs registers it on the hosting side and then shows you the precise DNS records to add, along with step-by-step instructions for your specific registrar. Doing this first means the values on screen are the ones you copy in the next step.
An A record points a bare domain at a numeric server address. In your registrar's DNS screen, add a new record:
- Type: A
- Name / Host: @ (this symbol means the plain domain with nothing in front of it; some registrars want it left blank instead)
- Value: the IP address SmashWebs shows you. Copy it straight from your dashboard, where it sits next to a copy button, rather than typing a number you read somewhere else.
A CNAME record points one name at another name instead of a number. It is how the www version of your address finds your site. Add a second record:
- Type: CNAME
- Name / Host: www
- Value: the target SmashWebs shows you. It looks like a web address rather than a number; copy it from your dashboard.
Leave the TTL field on its default or "Automatic" setting. TTL just controls how long the phone book caches your listing, and the default is fine.
Save the records at your registrar. Back in the SmashWebs Domain page, the status tracker walks through the stages automatically: domain added, DNS pending, DNS verified, then SSL active. When the last stage turns on, your site is live at your address over a secure (https) connection, with the certificate handled for you. You can press Check status now if you do not want to wait for the next automatic check.
Registrars often ship a new domain with a placeholder A record and a "parking" or "for sale" page pointed at it. If you add your new records but leave the old ones in place, your browser sees two conflicting listings and behaves unpredictably. Remove any existing A record on @ and any existing CNAME on www before you add the new ones. One A record on the apex, one CNAME on www, nothing else.
How Long Propagation Takes (and How to Check)
After you save, the change has to spread across the internet's network of phone-book copies. This is called propagation, and it is the part that requires patience rather than skill. Most changes take effect within an hour. Some take longer. The official answer is "up to 48 hours," but that is a rare worst case, not what you should expect.
You do not have to guess. Two easy checks:
- The status tracker on the SmashWebs Domain page. It re-checks on its own, and the Check status now button forces an immediate look.
- A free tool like dnschecker.org. Enter your domain and it shows whether your new records are visible from servers around the world yet. Green checkmarks mean propagation is working; a few stragglers are normal and resolve on their own.
Common Failure Modes (and the Fix for Each)
Only www works, or only the plain domain works
This means you added one record but not the other, or you put the right value on the wrong host. The plain domain needs the A record on @; the www version needs the CNAME on www. You want both so that clients reach you whether or not they type the www. Go back and confirm you have exactly one of each, on the correct host.
Stale or duplicate records
If the site still points somewhere old, you almost certainly have a leftover record fighting the new one. Delete any A or CNAME record on @ and www that does not match what SmashWebs shows you. Extra records are the single most common reason a connection "won't take."
Cloudflare: the orange cloud
If your DNS is at Cloudflare, each record has a cloud icon next to it. An orange cloud routes traffic through Cloudflare's proxy, which prevents the secure certificate from being issued and leaves your site broken. Click the cloud so it turns gray (labeled "DNS only") on both records. This one setting is the most common Cloudflare mistake.
Impatience
Sometimes nothing is wrong and the records simply have not finished propagating. If your entries match your dashboard exactly, there are no leftover records, and any Cloudflare clouds are gray, then wait an hour and check again before changing anything. Editing records you have already set correctly only resets the clock.
If the records match your dashboard, the old ones are gone, and it has been several hours with no change, contact SmashWebs support from your dashboard. We can see the connection status on the hosting side and tell you exactly which record is off, so you are not guessing in the dark.
What Happens Once You Are Connected
With your domain pointed and the secure certificate active, everything else runs on your real address: your pages, your core pages, and the technical files that help you get found. Every SmashWebs site generates its own sitemap.xml and robots.txt automatically, which matters for the very next thing you should do: tell Google your site exists.
That is a separate, quick job covered in our Google Search Console setup guide, which uses the same DNS screen you just visited to verify ownership. If you connected your domain successfully, you already have the skill required; you are adding one more record, a TXT record, in the same place.