Domain Setup
How to Point a Domain to Hosting Without Breaking Email or DNS
Whether you're launching a new site or moving an existing one, connecting your domain comes down to one of two settings — get it right and everything else follows.
2
Ways to connect a domain: nameservers or an A record
24-48h
Typical worldwide propagation window
Free
SSL issued automatically once DNS resolves
24/7
Human support if a record won't save
In short
To point a domain to hosting, either change the domain's nameservers at your registrar to your host's nameservers (the usual method, which hands over the whole domain), or add an A record pointing to your hosting server's IP address while keeping your current nameservers (useful if email or other services stay elsewhere). Most single-site setups should use nameservers; changes take up to 24-48 hours to propagate worldwide.
Hosting Cheap accounts include the exact nameservers or IP address in the welcome email, so you're never guessing which values to enter.
Buying a domain from one company and hosting from another is completely normal, but it's also where most "my website isn't showing up" confusion comes from. The domain and the hosting account only connect once you tell the registrar where to send visitors, and that comes down to one of two settings: nameservers, which hand over the entire domain's DNS to your host, or a single A record, which redirects just one hostname while leaving everything else — like existing email — untouched.
Hosting Cheap lists both options in your welcome email the moment your account is created, along with a cPanel-style panel for managing DNS records yourself if you need finer control. Free SSL issues automatically the moment your domain resolves here, and if you're moving an existing site, free managed migration means the content is already in place before you flip the switch.
Nameservers vs A Records: Which One Changes What
Nameservers control the entire DNS zone for a domain — every A, MX, TXT and CNAME record lives on whichever nameservers are assigned, so switching them hands the whole domain over to your new host in one move. That's the right choice when you're moving a complete website (and usually its email) to a new provider and want one place to manage all of it going forward.
An A record, by contrast, only redirects the traffic for one specific hostname to an IP address, leaving your existing nameservers and every other record — including MX records for email — exactly as they were. That's the better fit when a company's email or a separate subdomain needs to keep running on its current provider while just the main site moves.
Where to Make Each Change
Nameservers are changed at your domain registrar — wherever the domain itself was purchased or is currently managed — usually under a section labeled "Nameservers" or "DNS Management." You'll switch from the default option to a custom one and paste in the values your host provided.
An A record is changed in the registrar's DNS zone editor instead, by adding or editing a record with the host set to "@" (the root domain) and the value set to your hosting server's IP address. If you also want "www" to work, a matching CNAME or A record for that hostname needs adding too.
How Propagation Actually Works
Every DNS record carries a TTL (time to live) telling resolvers around the world how long to cache it before checking again. That's why a change can appear instantly for one visitor and take up to a day or two to show up for another — each internet provider and device caches independently rather than checking the source every time.
Seeing the old site on your phone while a colleague already sees the new one isn't a sign anything failed; it's just two different resolvers on different caching schedules. An online DNS propagation checker can confirm the new records are live globally well before every resolver has individually caught up.
Getting It Right the First Time
Enter nameservers or IP addresses exactly as provided, without extra characters, and change one method or the other, not both at once, which can create conflicting records. Leave your existing host running until you've confirmed the new one works, so there's never a window where the domain points nowhere.
Because free managed migration copies your site and database over before you touch DNS at all, the destination is already fully built by the time you make the switch — the domain change becomes the last, simplest step rather than something you're racing to finish alongside everything else.
Not Sure Which Method Fits Your Setup?
If you're moving the whole site and its email to a new host, nameservers are the simplest route — one change, one place to manage everything from then on, including any subdomains you add later.
If you need to keep email or another service hosted elsewhere while only the main site moves, a single A record for the root domain (and www) leaves those other records completely undisturbed.
- Nameservers hand over the whole domain's DNS to your new host
- A records redirect just one hostname, like the bare domain or www
- Existing MX and email records stay intact with the A record method
- Your welcome email lists both options with your exact values
Why Hosting Cheap
What you get
Both methods supported
Point your domain via nameservers or a single A record, whichever suits your setup.
Clear setup details
Your welcome email lists the exact nameservers and IP address for your account.
Free SSL once it resolves
A certificate issues automatically the moment your domain points here.
Free migration first
Your site's files and database move over before you switch the domain, so nothing sits half-finished.
cPanel-style panel
Add domains and edit DNS records yourself from one straightforward control panel.
24/7 human support
Get help from a real person if a record won't save or propagation looks stuck.
How It Works
Get set up in a few steps
Choose nameservers or an A record
Use nameservers for a full move, or an A record if email or other services need to stay put.
Update the setting at your registrar
Log in where the domain is registered and change the nameservers or add the A record.
Wait for propagation and confirm
Allow up to 24-48 hours, then check the site loads and SSL has issued before going public.
Included
Everything you need, on every plan
- Know whether you're changing nameservers or adding an A record
- Have your host's nameservers or IP address ready before logging in
- Confirm the domain isn't locked at the registrar before editing DNS
- Only change one method at a time, not both together
- Leave the old host running until the new one is confirmed working
- Check MX records if email is hosted separately from your website
- Allow up to 24-48 hours before troubleshooting a domain that "won't load"
- Verify free SSL has issued once the domain resolves
FAQ
Frequently asked questions
Should I use nameservers or an A record to point my domain?
Use nameservers if you're moving your whole domain — website, email and all — to the new host, since it hands over full DNS control in one step. Use an A record instead if you want to keep existing email or subdomains running on their current provider while only the main site moves.
How long does it take for a domain to point to new hosting?
Most changes finish propagating within a few hours, but it can take up to 24-48 hours for every resolver worldwide to catch up. During that window some visitors may briefly see the old site while others see the new one, which is normal.
Will changing nameservers affect my email?
Yes, because nameservers control every DNS record for the domain, including the MX records that route mail. If email is hosted separately from your website, either recreate those MX records on the new nameservers or use the A record method instead.
What if I only want my www subdomain to point here?
Add a CNAME or A record for just that subdomain rather than changing nameservers, which affects the whole domain. This is common when a company's root domain runs elsewhere but a specific project needs to live on new hosting.
Can I point a domain before my site is finished?
It's usually better to finish building and testing your site first, since visitors start reaching it as soon as DNS propagates. Free migration and a working preview URL mean everything can be ready before you flip the switch.
Why isn't my domain loading after I made the change?
In almost every case this is local DNS caching on your device, browser or ISP rather than a failed change — try a different network or an online DNS checker to confirm the new records are live. If it's still not resolving after 48 hours, contact support to check the setup.
Related hosting
Point Your Domain and Go Live Today
Get your nameservers or IP address instantly, plus free migration and free SSL, from $2.09/mo.
Get Started