How to point domain to hosting depends on whether you want your hosting company to manage all DNS records or only your website records. You can change the domain’s nameservers, or keep your current DNS provider and add an A record; the right choice mainly depends on where your email is hosted.
Step 1: Choose how to connect your domain
This first decision prevents you from moving the wrong DNS records or interrupting email.
DNS is the system that connects a readable domain such as example.com to an IP address that computers can use. ICANN describes DNS as the link between a domain name and its IP address in its DNS explainer.
You have two practical options:
| Method | What you change | Best when | Main caution |
|---|---|---|---|
| Nameservers | Replace the domain’s authoritative nameservers | Your new host should manage the full DNS zone | Copy existing email and verification records first |
| A record | Keep nameservers where they are and point web records to the new host | Email or other services must stay with another provider | You must maintain the DNS records yourself |
Use nameservers when the website, domain DNS and business email will all be managed at the new host. Use an A record when your email is elsewhere and you only want example.com and www.example.com to load from the new hosting account.
Changing a domain’s registrar is not required. You can leave the domain registered where you bought it and point it to hosting somewhere else.
Step 2: Prepare the domain and hosting account
Preparing both sides before editing DNS gives the new website somewhere to resolve and makes the final check easier.
You need:
- Access to the account where the domain is registered.
- Access to the hosting control panel.
- The exact nameservers or IPv4 address supplied by your hosting company.
- A note of the current DNS records, especially
MX,TXT,CNAME,AandAAAArecords.
Add the domain to your hosting account before changing DNS. In HostKarle’s DirectAdmin panel, add it as a domain and use the exact hosting details supplied for your account. If the domain is already attached, check the spelling and whether the website files are in the intended document root.
If you are moving email too, create the required mailboxes and copy the required mail records before the switch. If email will remain with another provider, do not delete its MX, SPF, DKIM or other verification records.
For a HostKarle domain connection, the nameservers are:
ns1.fastnsdns.com
ns2.fastnsdns.comYou can also read how to find HostKarle nameservers and update them before making the change.
Step 3: Method 1 — change the nameservers
Nameservers tell the internet which DNS servers are authoritative for your domain, so this method hands the full DNS zone to the new host.
1. Copy the new nameservers
Open your hosting welcome email or hosting panel and copy both nameserver hostnames exactly. Do not replace a hostname with an IP address, add a website URL, or use nameservers found in a random tutorial.
For HostKarle, enter ns1.fastnsdns.com and ns2.fastnsdns.com.
2. Open the domain’s nameserver settings
Sign in where you purchased the domain. Open the domain list, select the domain, and look for a menu named Nameservers, DNS, Domain settings or Manage DNS.
At a registrar such as GoDaddy, the label and screen layout can change, but the setting is still under the individual domain rather than under website forwarding. Choose the option for custom nameservers.
3. Replace the old entries
Remove the old nameservers and enter the new pair in the first and second fields. Do not mix one old nameserver with one new nameserver unless your hosting provider explicitly instructs you to do that. Save or confirm the change, and complete any email or two-factor verification requested by the registrar.
4. Recreate important records at the new DNS provider
After the change, the new authoritative DNS provider becomes the place where you manage records. Recreate any records that the website, email, payment service, analytics tool or search console needs.
At minimum, check these before assuming the switch is complete:
AandCNAMErecords for the website and subdomains.MXrecords for email.TXTrecords for SPF, DKIM, domain verification and other services.AAAArecords if you intentionally use IPv6.
Success looks like the domain showing the new nameservers in a public lookup and the new DNS zone containing all records you still need. Website and email checks may finish at different times while caches expire.
Step 4: Method 2 — add an A record
An A record maps a hostname to an IPv4 address, so this method changes website traffic while leaving your existing nameservers and unrelated DNS records in place. Cloudflare’s A-record guide explains the same mapping in more detail.
Use the hosting provider’s current IPv4 address. Do not guess it from an old screenshot, and do not use the IP address of a temporary preview URL. If the provider gives you a hostname rather than an IP address, follow its instructions for a CNAME instead.
1. Open the DNS zone editor
At the domain registrar or DNS provider, open the zone for the domain. Choose Add record or Manage DNS. Make sure you are editing the correct domain and not a subdomain.
2. Point the root domain
Create or edit the record for the root domain using values like these:
Type: A
Name: @
Value: YOUR_HOSTING_IPV4_ADDRESS
TTL: Auto or the provider's defaultSome panels show the root as the full domain name or leave the Name field blank instead of using @. Use the panel’s own description of the root or apex record.
3. Point the www version
Most sites need both the bare domain and the www version. If your host tells you to use a CNAME, create or edit this record:
Type: CNAME
Name: www
Value: yourdomain.example
TTL: Auto or the provider's defaultReplace yourdomain.example with your real domain. If your hosting provider gives a different target for www, use that exact target. Do not create a CNAME and an A record with the same name at the same time.
4. Keep email records intact
Leave the current MX records and email-related TXT records in place when email is staying with the existing provider. Also check for an old AAAA record: if it points to an old server and you do not use IPv6 there, it can send some visitors to the wrong destination even after the A record is correct.
Success looks like both the root domain and www resolving to the new hosting destination while email records still point to the mail provider you chose.
Step 5: Pick the right method for your setup
Use this quick decision table before saving a change:
| Your setup | Recommended method | What to check first |
|---|---|---|
| New host will manage website and email | Nameservers | Copy the current mail and verification records |
| Email stays at Google Workspace or another mail provider | A record | Keep MX, SPF and DKIM records unchanged |
| You want to manage DNS in one hosting panel | Nameservers | Confirm the new host imports or lets you recreate the zone |
| Only a subdomain should use the new host | A or CNAME record for that subdomain | Do not change the parent domain’s nameservers |
| You were given a hostname, not an IP address | CNAME where allowed | Use the host’s exact target and record instructions |
HostKarle’s domain service supports domains from ₹709/yr and lists the nameservers needed to connect a domain you already own. If you need to inspect the public registration and nameserver details, use the HostKarle WHOIS tool.
Step 6: Wait for DNS propagation
DNS changes are cached, so a successful save does not make every network see the new answer immediately.
Allow several hours for a normal change and up to 48 hours for nameserver changes to appear consistently worldwide. The exact time depends on cached TTL values, recursive DNS resolvers and the type of record you changed. Cloudflare’s DNS record documentation explains that TTL controls how long resolvers cache a DNS answer.
During this period, your own laptop and mobile phone may show different results. Do not keep changing the record every few minutes; each change can make it harder to tell which cached answer you are seeing.
You can check from more than one network:
- Open the domain in a private browser window on Wi-Fi.
- Check it again using mobile data.
- Query the domain with a DNS lookup tool and inspect its
NS,A,CNAMEandMXresults. - Ask someone on another network to test the domain if the change is urgent.
Step 7: Verify the website and email
Verification confirms that DNS is correct and that the hosting account is configured for the domain.
Check these URLs in a private browser window:
http://yourdomain.example
http://www.yourdomain.example
https://yourdomain.example
https://www.yourdomain.exampleThe expected result is your website, not a registrar parking page, a DNS error or another site’s default page. If HTTP loads but HTTPS does not, wait for the host’s SSL certificate process or check that the domain resolves correctly on both the root and www names.
Send a test email in both directions if you use the domain for business mail. Check the MX records rather than assuming that a working website means email is configured; website and email use separate DNS records.
Finally, sign in to the hosting panel and confirm that the domain is attached to the intended site directory. A correct DNS answer can still show a default page when the domain has not been added to the hosting account or is mapped to the wrong document root.
Troubleshooting common pointing errors
The domain shows “DNS_PROBE_FINISHED_NXDOMAIN”
Check that the domain is active, the nameservers are typed correctly and the DNS zone contains an A or CNAME record. If you just changed nameservers, wait for propagation and test from another network.
The old website still opens
This is often cached DNS, especially soon after an A-record edit. Query the domain from a different resolver or mobile network and compare the answer with the new hosting IP. Also check for an old AAAA record.
The website opens but email stops working
The new DNS zone may not contain the old provider’s MX, SPF or DKIM records. Restore the required records at the authoritative DNS provider, then allow mail DNS caches to refresh. This is why exporting or recording the DNS zone before a nameserver change matters.
The domain opens a default hosting page
DNS may already be correct. Check that the domain is added in the hosting panel, the files are in the correct document root, and the hosting account has selected the intended site for that domain.
Only www or only the bare domain works
Check the root A record and the www CNAME separately. Remove conflicting duplicate records and use the target recommended by your hosting provider. Test both versions after the records have propagated.
FAQ
Do I need to transfer my domain to my hosting company?
No. You can keep the domain registered with your current registrar and point it to a different hosting company using nameservers or DNS records. Transfer is a separate account and registrar process.
Is changing nameservers better than changing an A record?
Neither is automatically better. Nameservers are simpler when the new host should manage the whole DNS zone; an A record is safer for a setup where email or other services must remain with the current DNS provider.
How long does it take to point a domain to hosting?
Many DNS changes appear within minutes or a few hours, but nameserver changes can take up to 48 hours to be seen consistently. Check from more than one network while caches expire.
Will changing nameservers delete my website or domain?
No, changing nameservers does not delete the registration or your website files. It changes where DNS records are managed, so the website can appear unavailable if the new DNS zone or hosting account is not prepared correctly.
Can I point only a subdomain to another hosting account?
Yes. Keep the parent domain’s nameservers and create an A or CNAME record for the subdomain, such as blog. Add that subdomain to the destination hosting account as well, then verify blog.yourdomain.example separately.
Want to partner with us, suggest a resource or advertise on this blog? Email partnerships@hostkarle.in
