Domain Setup
Connecting a Domain You Registered Somewhere Else
Your domain doesn't need to move registrars to work with new hosting — pointing it there with a nameserver or record change is enough on its own.
2
Ways to connect: nameservers or individual records
24-48h
Typical worst-case DNS propagation window
Free
Managed migration help moving the site itself
24/7
Human support if DNS changes don't take
In short
To connect a domain bought at another registrar, log in to that registrar's account and either change the nameservers to the ones your host provides, or edit the domain's A record (and the www CNAME) to point at your hosting's IP address. Ownership and renewal stay with the original registrar; only where the domain points changes, and it typically takes anywhere from a few hours up to 24-48 hours to propagate fully worldwide.
Nameservers hand over full DNS management to the new host, while an A record change keeps DNS at the original registrar and only redirects the site itself — most site owners use nameservers since it's simpler to manage afterward.
A domain bought at GoDaddy, Namecheap, Google Domains or any other registrar works fine with hosting from a completely different company — the domain and the hosting are two separate services, and neither one requires you to move the other. The registrar keeps handling registration and renewal; the hosting account keeps handling the site's files, email and databases. The only thing that needs to change is where the internet is told to send visitors, and that's a DNS setting, not a domain transfer.
There are two ways to make that connection: switching the domain's nameservers to the new host's, which hands over full DNS management, or leaving nameservers alone and editing individual records (an A record for the root domain, a CNAME for www) to point at the hosting's IP address. Most site owners use the nameserver method because it's simpler to manage going forward, but the record-based method matters when email or other DNS-dependent services need to stay exactly where they are.
Method 1: Changing Nameservers (Full DNS Handover)
Changing nameservers is the more common route because it hands every DNS record — A records, MX records for email, CNAMEs, TXT records — over to the new host in one step. Your hosting welcome email or panel includes the nameserver addresses to use; log in to the original registrar's account, find the DNS or Nameservers section for that domain, replace the existing entries with the new ones, and save.
Once saved, the registrar stops answering DNS queries for the domain and the new host takes over completely, which means any custom records that lived at the old registrar (existing email routing, a TXT record for a service, a subdomain pointing somewhere else) need to be recreated inside the new host's DNS zone before the switch, not after — otherwise those services go dark for however long propagation takes.
Method 2: Editing A and CNAME Records (Leave Nameservers Alone)
If you want to keep DNS management at the original registrar — because email is already configured there through a separate provider, for instance — leave the nameservers untouched and instead edit the individual records. Point the domain's A record (the root, or '@') at your hosting account's IP address, and point the www CNAME at the target the hosting panel specifies.
This method only redirects web traffic; anything else set up in that registrar's DNS zone, such as existing MX records for email or other subdomains, is unaffected, which is exactly the point. It's the right choice when only the website itself needs to move and every other DNS-dependent service already works and shouldn't be touched.
Verifying the Domain Is Actually Pointing Correctly
DNS changes aren't instant, and checking immediately after saving them is the most common cause of false alarms. Use a DNS lookup tool to check the domain's current A record or nameservers from several locations at once, and expect the change to be visible in some regions before others — that's propagation working normally, not a sign anything's broken.
Once propagation looks complete, confirm the site loads correctly at the domain itself, not just the hosting's temporary IP address or a preview URL, that free auto-renewing SSL has issued for it, and that email — if it's meant to route through the new host — is actually arriving. A domain that loads the site but shows a certificate warning usually just needs a little more propagation time before SSL fully activates.
What Doesn't Change When You Connect (Rather Than Transfer)
Connecting a domain to new hosting leaves registration, renewal billing and the registrar account exactly where they were — you'll still renew the domain with the original registrar on its original schedule, and nothing about ownership or the WHOIS registrant record changes as part of this process. A domain transfer, moving the registration itself to a new registrar, is a separate and entirely optional process you never have to do.
This also means there's no rush and no risk window tied to a transfer's typical multi-day process or transfer lock — a nameserver or record change takes effect on its own propagation timeline, and if something looks wrong, reverting to the previous nameservers or records puts things back exactly as they were beforehand.
Bring Your Domain, Not Just Its Name
Whichever registrar a domain was bought from, connecting it to new hosting is a DNS change, not a migration project, and it's usually done inside fifteen minutes at the registrar's end.
Hosting Cheap provides clear nameserver details plus free managed migration for the site itself, so the domain and the content both land in the right place without guesswork.
- Nameserver details provided the moment hosting is set up
- Free managed migration for the site's files and database
- Free auto-renewing SSL issued once the domain resolves
- 24/7 human support for DNS or propagation questions
Why Hosting Cheap
What you get
Clear nameserver details
Get the exact nameserver addresses needed to point an existing domain at your new hosting account.
A record support for partial moves
Point just the website via A record while leaving email or other services on their current DNS setup.
Free managed migration
Get help moving the site's files and database over while the domain connection is being set up.
Free auto-renewing SSL
A certificate issues automatically once the domain resolves to the new hosting, at no extra cost.
NVMe SSD + LiteSpeed
The site the domain points to loads quickly the moment DNS propagation finishes.
24/7 human support
Real people can check nameserver or record settings if a domain doesn't resolve as expected.
How It Works
Get set up in a few steps
Get your new nameservers or IP
Find the nameserver addresses or hosting IP address provided in your hosting welcome email or panel.
Update DNS at the original registrar
Log in to the registrar where the domain is registered and change nameservers, or edit the A and CNAME records.
Verify propagation and check the live site
Confirm the domain resolves correctly, the site loads, and SSL has issued before considering the move complete.
Included
Everything you need, on every plan
- New nameserver addresses or hosting IP address confirmed
- Existing MX records and other subdomains noted before switching nameservers
- A record and www CNAME set correctly if using the partial-move method
- DNS lookup checked from more than one location after saving changes
- Site loads at the actual domain, not just a temporary hosting URL
- Free SSL confirmed active on the domain once propagation completes
- Email delivery tested if it's meant to route through the new host
- Previous nameserver or record values saved in case you need to revert
FAQ
Frequently asked questions
Do I need to transfer my domain to use it with new hosting?
No. Connecting a domain only requires changing where its DNS points — either its nameservers or specific records — while the domain stays registered exactly where it was. A domain transfer, moving the registration itself, is entirely optional and separate.
How long does it take for a domain to point to new hosting?
Most DNS changes are visible within a few hours, though full worldwide propagation can take up to 24-48 hours in some cases. Testing from multiple locations, rather than just your own connection, gives a more accurate picture of how far along it is.
Should I change nameservers or just the A record?
Change nameservers if you want the new host to manage all DNS for the domain going forward — it's simpler for most site owners. Edit only the A and CNAME records if email or other services already work through the existing registrar's DNS and shouldn't be disturbed.
Will changing nameservers break my existing email?
It can, if the email's MX records aren't recreated in the new host's DNS zone before or immediately after the switch. Note down the existing MX records at the old registrar first, then add matching ones at the new host so email keeps routing correctly.
Why does my domain show a certificate warning right after pointing it?
This is usually propagation still finishing or free SSL not having issued yet, both of which resolve on their own within a short window. If a warning persists well after the domain is fully resolving, that's worth checking with support directly.
Can I point more than one domain at the same hosting account?
Yes, addon domains and subdomains can point to the same hosting account, each with their own DNS settings pointing at the same server. Each additional domain still goes through the same nameserver or A record process individually.
Related hosting
Ready to Point Your Domain at Faster Hosting?
Get NVMe SSD hosting with free SSL and free managed migration, from $2.09/mo.
Get Started