Building a site in Bolt, Lovable, Wix or Framer can take an afternoon. Getting it onto your own domain, with a secure connection and working email, can take a week of confused tabs. That is not a sign you did anything wrong. Hosting and DNS are genuinely confusing, and the tools rarely explain how the pieces connect.
Here is the short version, in plain English.
Two different places, two different jobs
Your website lives in two places that people often mix up.
- The host is where your site’s files actually run. That might be Netlify, Vercel, or the builder’s own hosting.
- The registrar is where you bought your domain name, such as GoDaddy, Namecheap, Squarespace Domains or Cloudflare.
The registrar doesn’t hold your website. It holds the directions to your website. Those directions are called DNS.
DNS records, without the jargon
DNS is the internet’s address book. When someone types your domain, DNS tells their browser where to go. The two records you will see most:
- A record: points your domain to a numeric server address (an IP address). Usually used for the bare domain, like yourbusiness.com.
- CNAME record: points one name at another name. Usually used for www, pointing it to an address your host gives you.
Your host tells you exactly which values to use. The job is entering them correctly, in the right place, without disturbing anything else.
Change only the records your host asks for. Everything else in your DNS is there for a reason.
www or no www
Decide on one main version of your address, either www.yourbusiness.com or yourbusiness.com, and make the other one redirect to it. Both should work. Only one should be the “real” one. This keeps your links tidy and helps search engines treat your site as a single site instead of two.
SSL, the padlock
SSL is what puts “https” and a padlock in the address bar. On modern hosts, it is usually automatic and free once your DNS is pointing correctly. If you see a security warning right after connecting a domain, it often just means the certificate hasn’t been issued yet. Give it time, then check both the www and non-www versions.
Propagation: why it works for you but not your friend
DNS changes don’t update everywhere at once. Different networks remember old answers for a while. For a few hours, your site may load on your phone but not your laptop. That is normal. Panicking and changing records again usually makes it take longer.
What people miss
- Deleting or overwriting MX records, which route your email. This is the most common way people lose email for days.
- Forgetting other email records, like SPF and DKIM (TXT and CNAME records that prove your email is legitimate).
- Leaving both www and non-www live without a redirect.
- Pointing the domain at the host but never adding the domain inside the host’s settings, so the host doesn’t know to answer.
- Still sharing the builder subdomain (like yoursite.netlify.app or yoursite.lovable.app) in links, bios and ads after moving.
- Letting the domain lapse because auto-renew was off or the card on file expired.
- Using DNS settings at the registrar when the domain’s nameservers actually point somewhere else, so the changes do nothing.
How AftUp handles it
On any plan, we get your site live on its own domain in the first month. That means we:
- Confirm where your site is hosted and where your domain is registered.
- Record your existing DNS, especially email records, before touching anything.
- Add the correct records, set your main address and redirect the other.
- Wait out propagation and confirm SSL is working on every version of the address.
- Help you swap the old builder subdomain for your real domain wherever it appears.
After launch, every plan includes 24/7 uptime and SSL monitoring, so we hear about an outage or an expiring certificate before your customers do. Growth and Scale add hands-on hours for fixes and a faster response when something needs attention. You keep ownership of your domain, your hosting account and your code the whole time. See how it works or our launch help page for more.
Do it yourself
If you’d like to try it on your own, here is the order that avoids most trouble:
- Find out where your domain’s nameservers point. That is where your DNS is actually managed.
- Screenshot or copy every existing DNS record before you change anything.
- Add your domain inside your host’s settings first, so it gives you the exact records to use.
- Add only those records at your DNS provider. Leave MX and other email records alone.
- Pick www or non-www as your main address and set the redirect at your host.
- Wait. Check again in an hour, then a few hours later.
- Confirm both versions of your address load with the padlock, and send yourself a test email.
If anything about your current setup feels unclear, a free site check will tell you where things stand before you change a thing.