To change nameservers in Hostinger, log into your hPanel, go to the Domains section, select your domain, click DNS or Nameservers on the left menu, choose "Change Nameservers," and enter the new addresses. You need at least two valid nameserver records to complete the update. Propagation takes up to 24 hours globally. This process applies to domains registered through Hostinger or connected to a Hostinger hosting plan.
The exact steps to change nameservers in Hostinger
Changing where your domain points requires updating specific records inside your control panel. The estimated time for this task is five minutes. The difficulty level is beginner.
- Log into your Hostinger account and open the hPanel dashboard.
- Click the "Domains" tab located in the top navigation menu.
- Select the specific domain name you want to modify from your list of registered domains.
- Click "DNS / Nameservers" in the left-hand sidebar menu.
- Find the Nameservers section and click the "Change" button next to your current records.
- Select the option labeled "Change Nameservers."
- Type the new nameserver addresses provided by your destination host into the input fields.
- Add at least two nameservers. Click the plus icon if you have three or four to enter.
- Click "Save" to apply the changes to your domain.
Warning: Changing these records disconnects your domain from your current Hostinger hosting environment immediately after propagation finishes. Any active websites or email accounts tied to the old server will stop working until you recreate them on the new host.
Note: If you manage your domain's DNS through Cloudflare instead of Hostinger, changing the records here will not work as expected. You must update them directly inside your Cloudflare dashboard instead.
After clicking save, the update begins spreading across the internet. Most visitors see the change within four to eight hours. Some regions take the full 24 hours to recognize the new routing path. During this window, some visitors might reach the old server while others land on the new one. ICANN's official documentation confirms that global DNS propagation follows this timeline due to how caching works across different regional networks.
Why you might point your domain away from default Hostinger servers
Hostinger assigns its own default nameservers (ns1.dns-parking.com and ns2.dns-parking.com) when you register a domain or buy a hosting plan. People change these defaults for several practical reasons.
Moving a website to a different hosting provider is the most common reason. Your new host gives you their specific server addresses during setup. Entering those addresses tells the internet to send traffic to the new company's machines instead of Hostinger's.
Switching to a third-party DNS manager like Cloudflare is another frequent cause. These services route your traffic through their global network before it reaches your web server. They provide custom addresses to paste into your registrar's panel. This setup often improves load times and adds security layers against traffic spikes.
Setting up a private DNS infrastructure also requires an update. Businesses running their own servers use internal addresses to maintain strict control over their routing records. This approach keeps everything within a single managed environment rather than relying on a shared registrar setup.
Understanding the difference between nameservers and DNS records
A nameserver acts as a directory for your domain. It tells the internet which specific server holds all the routing instructions for your website and email. When someone types your URL into a browser, their computer asks your assigned nameserver where to find the actual website files.
DNS records are the individual instructions stored on that server. An A record points your domain to a specific IP address. An MX record directs incoming emails to your mail server. A CNAME record creates an alias for subdomains.
When you change your nameservers in Hostinger, you hand control of all those individual records over to the new provider. The old A records, MX records, and TXT records stay behind on Hostinger's system. Your new provider starts with a blank slate unless they import your previous settings automatically.
This distinction matters because many people try to fix a missing email or a broken subdomain by editing individual records in hPanel after they already pointed the domain elsewhere. Those edits do nothing because Hostinger no longer controls the routing path. All record management must happen at the new destination once the switch completes.
How to change nameservers in Hostinger without breaking your live site
Taking your website offline during a migration causes lost revenue and frustrated visitors. Planning the transition prevents downtime.
First, set up your complete website on the new hosting provider before touching any settings in hPanel. Upload your files, import your database, and recreate every email account you currently use. The new server needs to be fully ready to accept traffic.
Second, copy all existing DNS records from your Hostinger panel. Write down every A record, CNAME, and MX entry. Recreate these exact records in your new host's control panel. Missing even one record can break a contact form or stop incoming emails.
Third, lower the TTL (Time to Live) value on your existing records 24 hours before making the switch. Setting the TTL to 300 seconds forces internet providers to check for updates more frequently. This step speeds up the transition and reduces the time visitors spend caught between the old and new servers.
Fourth, make the update in hPanel during your lowest traffic period. Check your analytics to find when the fewest people visit your site. Making the change at 3 AM means fewer visitors experience the transition phase.
If you are moving to a service like Cloudflare, follow their specific setup wizard. They usually scan your existing records automatically, but verifying the imported data manually prevents mistakes.
What happens if something goes wrong during the update
Mistakes happen when typing long server addresses. Knowing how to fix them saves hours of panic.
Problem: Your website shows a "server not found" error after the update.
Fix: Double-check the spelling of the addresses you entered in hPanel. A single missing letter or extra space breaks the connection. Log back into your Hostinger account, return to the DNS section, and correct the typo. Save the changes again.
Problem: Your website loads correctly, but incoming emails stopped arriving.
Fix: Your MX records did not transfer to the new provider. Log into your new host's control panel and add the required mail exchange records. Ask your new host's support team for the exact values needed to route email properly.
Problem: The changes have been saved for over 48 hours and your site still points to the old Hostinger server.
Fix: Clear your local DNS cache. On Windows, open Command Prompt and type "ipconfig /flushdns". On Mac, open Terminal and type "sudo dscacheutil -flushcache". Your computer might be holding onto an old version of the routing path. Restarting your router also clears cached data at the network level.
Common mix-ups people run into
Mix-up: Assuming that changing the nameservers automatically moves your website files and databases to the new host.
Reality: Updating these records only changes the routing direction. You must manually migrate all files, databases, and configurations to the new server before or immediately after making the switch. The new host does not pull content from the old one automatically.
Mix-up: Believing the update happens instantly for everyone worldwide.
Reality: Internet service providers cache routing data to speed up browsing. Different providers refresh their caches at different intervals. Visitors in New York might see the new server while visitors in London still connect to the old one for several hours.
Mix-up: Thinking you can edit individual A records in hPanel after pointing the domain to a different provider.
Reality: Once you assign new nameservers, Hostinger loses authority over your DNS zone. Any changes made inside hPanel are ignored by the rest of the internet. You must manage all future records through the new provider's dashboard.
Pointing a domain to Hostinger instead of away from it
Sometimes the goal is the reverse. You might have a domain registered at GoDaddy or Namecheap and want to host the actual website on Hostinger. The logic remains identical, but the direction flips.
Instead of entering a third party's addresses, you enter Hostinger's default values. For most standard plans, these are ns1.dns-parking.com and ns2.dns-parking.com. You paste these into the control panel of the company where you bought the domain.
This approach lets you keep your billing separate. You pay one company for the domain registration and pay Hostinger for the hosting space. Many people prefer this setup so they retain ownership of their domain name even if they decide to cancel their hosting subscription later.
If you are looking for affordable hosting to point your domain toward, checking current pricing helps. We track active promotions regularly, and applying a discount code during checkout lowers the initial cost significantly. Getting the best available rate before migrating makes the whole process cheaper.
Managing DNS locally versus changing nameservers entirely
You do not always need to change your nameservers in Hostinger to point a website somewhere else. There is an alternative method called managing DNS locally.
Instead of handing control over to a new provider, you leave Hostinger's default nameservers exactly as they are. Then, you go into the DNS Zone Editor inside hPanel and change the primary A record. You replace Hostinger's server IP address with the IP address of your new host.
This method keeps your email routing and other records intact. If your email runs through Hostinger but your website lives on a VPS elsewhere, changing only the A record solves the problem without disrupting your inbox.
The downside is that you now manage your website's routing from a panel disconnected from the actual server. If your new host asks you to verify domain ownership via a TXT record, you have to add that record inside hPanel rather than their own dashboard. It adds a layer of complexity for troubleshooting later.
What this means for your website going forward
Updating your routing records is a permanent administrative action until you decide to change them again. Once propagation finishes, your relationship with the old hosting environment ends completely. You should cancel any unused subscriptions at the old provider to avoid paying for empty server space.
Keep a written record of your new server addresses somewhere safe outside of your hosting dashboard. If you ever lose access to your new account, having those details written down allows you to point the domain back to Hostinger temporarily while you recover your credentials.
For readers who are setting up a fresh project and need reliable hosting before configuring their domain, we maintain background information on how we evaluate these platforms. Using our current verified discounts brings the price down significantly for new signups. If you have questions about specific setups, reaching out through our contact page is the fastest way to get help.
Ready to start your new hosting plan? Use the code hHostCouponHub at checkout to get 85% off your purchase through this Hostinger link.
Frequently asked questions
How long does it take to change nameservers in Hostinger?
The act of saving the new records in hPanel takes less than a minute. However, the global propagation process takes anywhere from 4 to 24 hours. During this window, different parts of the world will resolve your domain to different servers.
Can I change nameservers in Hostinger for a domain registered elsewhere?
No. You can only modify these records inside hPanel for domains that are either registered directly through Hostinger or transferred to their management system. If your domain lives at another registrar, you must log into that specific company's dashboard to make the update.
Will my website go down when I update my nameservers?
Your site stays online if you prepare the new server completely before making the switch. Downtime occurs when people change the records before uploading their website files to the destination host. Always migrate your content first, then update the routing path last.
Does changing nameservers affect my SSL certificate?
Yes. SSL certificates are tied to the specific server environment where they were issued. Moving to a new provider invalidates the old certificate. You must generate and install a new SSL certificate on your new host after the propagation finishes to keep your HTTPS connection active.
Once you finish updating your records and confirm your website loads from the new server, take a moment to test every page, submit a test contact form, and send a test email. Verifying these functions immediately catches any missing DNS entries before your visitors notice them. Grab your hosting plan using code hHostCouponHub for 85% off through our partner link to get started today.
This page contains affiliate links. If you purchase through the links on this page, we may earn a commission, at no extra cost to you.
