How to Connect Hostinger Domain to Another Hosting (Step-by-Step Guide)
Connecting your Hostinger domain to another hosting provider is something thousands of website owners do every year, whether they're switching to a faster host, moving to a VPS, or hosting their app on a platform like AWS, DigitalOcean, Netlify, or Render.
The good news is that your domain and your hosting are completely separate things. Buying a domain from Hostinger doesn't lock you into Hostinger's servers forever. You can keep your Hostinger domain and point it anywhere you want.
This guide covers exactly how to connect a Hostinger domain to another hosting provider using both major methods, changing nameservers and updating DNS A records — so you can pick whichever one fits your setup.
What's Actually Happening When You "Connect" a Domain
Before touching a single setting, it helps to understand what you're doing and why. Your domain is like a street address. Your hosting provider is the building at that address. Right now, your Hostinger domain points to Hostinger's servers by default. When you move to another host, the building changes — but you want to keep the same street address.
If you've just moved your site to another hosting provider, the domain might still be tied to the old hosting company and will not direct visitors to your website. You need to connect the domain name to the new web host.
Nameservers are the "GPS" for your domain. Changing your nameservers tells the entire internet to get all DNS instructions — for your website, email, and everything else — from your new hosting provider. Changing only the A record points just your web traffic to the new host's IP address.
These are your two options, and this guide walks through both.
Two Methods to Connect Your Hostinger Domain to Another Host
Method 1: Change Nameservers (Recommended for Most People)
This is the cleanest and most complete method. Changing nameservers is the preferred method if you want to fully move your domain's DNS zone management, including email records, to your external service provider.
Think of it like handing the entire phone book over to your new host. They manage everything from that point — your website records, email records, and any subdomains.
Step 1: Get the Nameservers from Your New Host
Find a list of nameservers from the new hosting provider. This information is usually provided in the company's documentation or in the post-purchase email. Web hosts usually provide two or more nameservers.
These values typically look something like ns1.yournewhost.com and ns2.yournewhost.com. Some hosts give you IP addresses for the nameservers too — note those down as well if provided.
Step 2: Log Into Hostinger hPanel and Open Your Domain Settings
At Hostinger, you can easily change the NS records by opening the Domains section and selecting your domain. Then proceed to the nameservers management page by clicking the Change button. Choose the Change nameservers option, enter the new nameservers, and click Save.
You'll see two options on that screen: keep Hostinger's nameservers or switch to custom ones. Choose custom and paste in the values your new host gave you.
Step 3: Wait for DNS Propagation
After making DNS changes such as updating nameservers, allow up to 24 hours for propagation. During this time, your website and domain management may be temporarily unavailable. Typically, changes take effect within a few hours.
One important heads-up: changing your domain's nameservers sets your email-related records for your new provider. If you already use a different email service, make sure to update the MX records with those of your email provider after the nameserver change has fully propagated.
Method 2: Update the A Record Only (Keep Hostinger as DNS Manager)
This method makes sense when you want to keep Hostinger managing your DNS — maybe you're using Hostinger Email or have other services like subdomains already configured there. You're only pointing your website traffic to a new server, not handing over full DNS control.
This method is suitable if you want to keep using Hostinger nameservers and manage your domain's DNS records in Hostinger. Before adding new A records, it is recommended to delete any existing ones.
Step 1: Find Your New Host's IP Address
Log into your new hosting provider's dashboard and find the server IP address assigned to your account. It will look something like 123.45.67.89. This is what you'll put into Hostinger's DNS zone.
Step 2: Open Hostinger's DNS Zone Editor
In hPanel, navigate to Domains, click Manage next to your domain, and open DNS / Nameservers from the left sidebar. The DNS records tab leads to the DNS zone management area, where you can add, edit, and delete records.
Step 3: Edit the A Record for Your Root Domain
Find the A record where the Name field shows @. This is your root domain (e.g., yourdomain.com). Click Edit, replace the current IP with your new host's IP address, and click Update.
Step 4: Update the www Record
You also need to make sure www.yourdomain.com points to the right place. If your provider instructs you to add a CNAME record for www, you can do so by following Hostinger's CNAME management guide. Otherwise, add or update the A record for www to the same IP address as your root domain.
Your DNS table should look like this after both updates:
Record Type
Name
Value
A
@
Your new host's IP
A or CNAME
www
Your new host's IP or alias
Step 5: Save and Wait
Save your changes and give DNS propagation time to do its thing. Once the nameservers or DNS records are set, wait for the changes to take effect. This period is called worldwide DNS propagation and can take up to 24 hours.
Which Method Should You Choose?
Here's a quick comparison to help you decide:
Nameserver Method
A Record Method
Best for
Moving everything to a new host
Pointing only web traffic elsewhere
Email records
Moves with DNS
Stays at Hostinger
Difficulty
Easy — just paste two values
Moderate — manual per-record edits
DNS control
Handed to new host
Stays with Hostinger
Recommended?
Yes, for most people
When keeping Hostinger email
The recommended method is to change the domain's nameservers. This transfers the domain's DNS control to the new hosting provider without changing the registrar. The A record method will only change the A records — all other records such as MX or TXT will stay unchanged and may not work at the new host.
Before You Make Any Changes — Do This First
Switching DNS settings without preparation can cause temporary downtime and broken email. Before making any changes, document or take screenshots of your current DNS settings, including A, MX, CNAME, and TXT records. This will be crucial if you need to revert or re-enter these settings in the new nameserver environment. Also check your email settings — if your email is hosted using the same domain, ensure you have the MX records and any other necessary email configuration details ready to set up on the new nameservers.
Also: schedule the nameserver change during a low-traffic period for your website to minimize the impact on visitors and services. Running a blog or e-commerce site? Do it at 2am on a Tuesday, not Friday afternoon.
If you're still in the market for a domain before setting any of this up, you can grab one affordably right now using a Hostinger 20% off domain renewal coupon code, useful whether you're buying your first domain or adding one for a new project.
Connecting to Specific Hosting Providers
Pointing Hostinger Domain to cPanel Hosting (Bluehost, SiteGround, etc.)
Log into your cPanel host and find the server IP address from the Account Details or Hosting Info section. Then go into Hostinger's DNS Zone Editor, update the @ A record with that IP, and add or update the www CNAME or A record to match. These hosts generally also provide their own nameservers, so you can use the nameserver method instead for a cleaner setup.
Pointing Hostinger Domain to VPS (DigitalOcean, Linode, Vultr, etc.)
Your VPS will have a static public IP address shown in the server dashboard. Use that IP in Hostinger's A records for @ and www. Find the Website IP Address in your hosting sidebar — it will be a string of numbers like 123.45.67.89. Copy this IP address, then navigate to your domain's DNS Management page and update the A record for the root domain.
Pointing Hostinger Domain to Netlify or Render
Platforms like Netlify and Render typically give you a CNAME value (like your-site.netlify.app) rather than a bare IP address. In that case, you can't use a CNAME for the root domain @ on most DNS setups. You'll either need to use their nameservers or add an A record pointing to their load balancer IP (which they'll specify in their domain settings). Check the platform's domain connection documentation for the exact values.
What to Do After DNS Propagates
Once your domain is successfully pointed to your new host, run through this checklist:
Visit your domain in a browser — make sure the new site loads correctly
Test both www and the root domain — both should reach the same place
Check email — send a test email to confirm MX records are working
Install or renew SSL — your new host usually handles this automatically, but verify HTTPS is active
Use a propagation checker — tools like whatsmydns.net let you see how your DNS changes have spread across global servers
If you get a 403 error when accessing your website after migration, it might be due to DNS propagation — different hosting plans have different IP addresses, so the A record change is still undergoing propagation. Give it some time and your site will work correctly.
Common Mistakes to Avoid
Forgetting to update MX records
If you used the A record method but forgot to check your MX records, your email will stop working. Your A record moved your web traffic, but your MX records — which control email — might still be pointing to your old host.
Editing DNS while DNSSEC is enabled
Make sure DNSSEC is disabled before making nameserver or DNS changes — you can verify this using a DNSSEC Checker tool. Active DNSSEC can prevent nameserver changes from taking effect.
Deleting records without backing them up
If you wipe your DNS zone and forget your old MX, SPF, or TXT records, rebuilding them from scratch can be painful — especially for email authentication settings like DKIM and DMARC.
Assuming it's instant
DNS propagation is not instant. Some internet service providers cache DNS responses for hours. If your site isn't loading on the new host right after the change, that's normal — just wait.
A Note for Students and First-Time Users
If you haven't bought your Hostinger domain yet and you're setting up your first project, students get especially good deals. Check out the Hostinger 80% off student discount to see what's available — pairing a discounted Hostinger domain with affordable external hosting on a VPS or cloud platform is a smart way to build real-world projects without spending much.
Quick Recap: How to Connect Hostinger Domain to Another Hosting
Get the nameservers or IP address from your new hosting provider
Log into Hostinger hPanel and go to Domains > Manage > DNS / Nameservers
For nameserver method: Click Change, enter new nameservers, and save
For A record method: Edit the @ A record with your new host's IP, then update the www record
Wait up to 24 hours for DNS propagation
Check your site, email, and SSL once the new settings take effect
The whole process takes about 10 minutes of actual work. The rest is just waiting for the internet to catch up — which, honestly, feels longer than it is. Once your domain resolves to your new host, you're fully up and running with your Hostinger domain pointing exactly where you want it.