How to Change Nameservers in Hostinger

How to Change Nameservers in Hostinger

To change nameservers in Hostinger, log into hPanel, open Domains, select your domain, and go to DNS / Nameservers. Click Change Nameservers, then either keep Hostinger’s nameservers or enter up to four custom nameservers from your new provider and save. Nameservers define who manages a domain’s DNS zone and map domain names to IP addresses, so this change moves DNS control without moving the registration itself.

The option only exists for domains managed inside Hostinger. DNS management in hPanel is available only when the domain uses Hostinger’s nameservers, and if DNS lives at another provider you must manage it there. Exact button and tab labels can vary slightly between accounts and interface updates, so treat the paths below as a guide to the current layout rather than a guarantee of every word on screen.

Before You Switch Nameservers

Changing delegation is quick, but the consequences are not automatic. Work through this checklist first so your website and email keep working.

  • Get the destination nameservers. Ask your new hosting or DNS provider for their nameserver hostnames. Some hosts also require IP addresses alongside the hostnames.
  • Migrate first. Upload your site files, import the database, and recreate mailboxes at the new provider before you change delegation.
  • Copy your DNS records. Nameservers move the whole zone, so MX, TXT, and other records must exist at the new provider. A record-only move changes just the A records, leaving MX and TXT unchanged and non-functional at the new host.
  • Note your current DNS state. Hostinger keeps DNS snapshots, and for risky changes such as switching email providers or re-pointing a live site, the documentation advises noting the current snapshot time so you know exactly what to restore.
  • Leave TTL alone unless you have a specific reason. The default TTL in Hostinger’s record editor is generally fine to keep.

If you use Hostinger Email, the Email Domain Settings page sets up MX, SPF, DKIM, and DMARC automatically, so do not add those records by hand.

How to Change Nameservers in Hostinger, Step by Step

The hPanel flow is short. The exact labels may shift over time, but the current path is:

  1. Log in to hPanel.
  2. Go to Domains and click the domain you want to change.
  3. Open DNS / Nameservers.
  4. Click Change Nameservers.
  5. Choose whether to keep Hostinger’s nameservers or enter custom ones. The form accepts up to four custom nameservers.
  6. Save the change.

If the domain already uses a *.dns-parking.com pair, Hostinger’s documentation says to keep that pair rather than replacing it. Hostinger nameserver pairs differ per domain, so never guess a pair or copy one from another guide or domain. You can confirm your exact values in hPanel. The DNS Zone Editor is also reachable from a website’s dashboard sidebar if you need to check records without leaving the site view.

What Happens to DNS Records, Email, SSL, and Your Site

When you switch, DNS authority moves to the new provider, and the records that were live at Hostinger stop being authoritative. Three practical consequences follow.

Your website depends on the destination zone. After the switch, check that your domain’s A records point correctly at the new server.

Email depends on recreated MX records. If the destination zone lacks mail records, incoming mail will not arrive. Recreate the MX, SPF, DKIM, and DMARC values at the new provider before or immediately after the change.

SSL should be reissued at the destination. Certificates are issued for a specific server environment, so plan to install a current certificate at the new host. Hostinger’s documentation does not specify certificate reissuance timing after a delegation change, so confirm the process with your destination provider.

DNSSEC deserves a separate check. Hostinger’s DNSSEC tab accepts a key tag, algorithm, digest type, and digest, but the stored guidance does not cover what happens to DNSSEC validation when you move delegation away from Hostinger. If DNSSEC is active on your domain, ask both providers how the DS records should be handled before you switch.

How Propagation Works and How to Verify the Change

DNS changes can take up to 24 to 48 hours to propagate globally, and often resolve sooner. Hostinger’s tutorial gives a shorter headline figure of up to 24 hours. Treat both as rough upper bounds: the actual time depends on resolver caching and on the TTL values involved.

Hostinger recommends checking propagation status at dnschecker.org or whatsmydns.net. Look at the NS records for your domain specifically, since those confirm the new delegation, and then check A and MX records to confirm the destination zone is answering correctly.

If your browser still shows the old server after public checkers agree the change has propagated, the problem is usually local caching. Clear your system DNS cache and retry, or test from a different network.

Common Problems and How to Fix Them

The form rejects your nameservers. Check for typos, extra spaces, and missing dots. Use hostnames rather than IP addresses unless your destination provider specifically supplies addresses.

The site loads but email stops. The destination zone is probably missing MX records. Add them at the new provider and ask its support team for the exact values.

The site still resolves to Hostinger after two days. Confirm in a public checker that the NS records changed. If they did not, re-open the nameserver settings in hPanel and re-save. If they did, flush your local DNS cache and test from another network.

You manage DNS at Cloudflare. Changing records in hPanel will not take effect if Cloudflare is authoritative. Make the change in the Cloudflare dashboard instead. The stored guidance does not cover Cloudflare proxy behavior in detail, so follow Cloudflare’s own documentation for proxied records.

How to Roll Back or Correct Wrong Nameservers

If you entered the wrong values, go back to DNS / Nameservers in hPanel, click Change Nameservers, and enter the correct pair or restore Hostinger’s own values. Hostinger keeps snapshots of your DNS zone, so a bad DNS edit is recoverable: open the domain’s DNS page, find DNS snapshots (also labeled Restore DNS Snapshot), pick a snapshot from before the change, and restore it.

If the interface will not accept your values or the change does not take effect after a reasonable propagation window, contact Hostinger support with the exact values you are trying to enter and the error message you see. If the problem is on the destination side, such as missing records or an unverified zone, the destination provider is the right contact.

Pointing an Externally Registered Domain to Hostinger

To move a domain the other way, register or transfer it elsewhere and enter Hostinger’s nameservers at that registrar. You can find Hostinger’s nameserver values on the Plan Details page in the Hostinger dashboard.

The familiar dns-parking.com pair is a common default, but pairs vary per domain, so copy the exact values shown for your account rather than assuming the standard pair applies. If the domain already uses a dns-parking.com pair, keep it. The exact process at the registrar varies by company.

Changing Nameservers vs. Editing DNS Records Locally

You do not always need to change delegation. If you only need to point the website at a new server while keeping email and other records at Hostinger, edit the A record in the DNS Zone Editor instead.

Factor Change Nameservers Edit DNS Records Locally
What moves The whole DNS zone, including MX and TXT Only the records you edit, such as the A record
Who manages DNS afterward The new provider Hostinger
Best for Full hosting migrations Splitting website and email across providers
Main risk Missing records at the destination break site or email Records live in two panels, which complicates troubleshooting

The local-edit route keeps your email routing intact, but it means future verification records, such as a TXT record a new host asks for, must be added in hPanel rather than at the new host.

After the Switch: A Short Verification Checklist

Once propagation settles, confirm the outcome rather than assuming it. Check that the domain resolves to the new server and that A records point correctly. Send and receive a test email, submit a contact form, and load a few key pages over HTTPS. Then cancel any hosting or email subscriptions you no longer use at the old provider, and store the new nameserver values somewhere outside the hosting dashboard so you can restore delegation if you ever lose account access.

Ready to set up hosting for a domain you are pointing at Hostinger? You can use the code hHostCouponHub at checkout for 85% off through this Hostinger link. You can also review our tracked active promotions and the current discount details before you buy.

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.

Leave a Comment

Your email address will not be published. Required fields are marked *

Scroll to Top