To connect an external domain — one registered at Namecheap, GoDaddy, Cloudflare, or any other registrar — to Hostinger, you have two methods: change the domain’s nameservers to Hostinger’s (ns1.dns-parking.com / ns2.dns-parking.com) and add the domain in hPanel, or keep your current DNS and point an A record at your Hostinger server IP. The nameserver method is simpler and unlocks Hostinger’s one-click DNS and email setup; the A-record method keeps DNS where it is, which Cloudflare users usually prefer. Either way, finish by adding the domain in hPanel under Domains, then allow a few hours for propagation.
Before you start: what you need
- The domain registered and unlocked for management at your current registrar (you do not need to transfer it — management and registration can stay where they are).
- An active Hostinger hosting plan with a free slot for the domain. If you have not bought hosting yet, any web hosting plan works for standard sites.
- Your Hostinger server IP address (hPanel → Hosting → Plan details) — needed only for the A-record method.
Method 1 — Change nameservers to Hostinger (recommended)
This hands full DNS control to Hostinger: one dashboard for the website, email records, subdomains, and SSL. Best for most people, especially if your current registrar’s DNS panel is clunky.
Step 1 — Get Hostinger’s nameservers. For web and cloud hosting plans these are ns1.dns-parking.com and ns2.dns-parking.com (checked against Hostinger’s documentation, October 2026). Confirm yours in hPanel under Hosting → Plan details, since older or VPS plans can differ.
Step 2 — Replace the nameservers at your registrar. Log in where the domain is registered — not in Hostinger — and find the nameserver/DNS settings. The labels vary:
- Namecheap: Domain List → Manage → Nameservers → Custom DNS → paste both Hostinger nameservers → save.
- GoDaddy: My Products → Domains → pick the domain → DNS → Nameservers → Change → enter custom nameservers → Save.
- Porkbun / Namesilo / Dynadot: domain management → Nameservers → switch from default to custom and enter the two Hostinger nameservers.
Replace all existing nameservers — never mix old and new, or DNS answers will alternate randomly between hosts and your site will flicker between the old and new server.
Step 3 — Add the domain in hPanel. In hPanel go to Domains and use Add Domain (or “Add website”), typing the full domain name. This tells Hostinger’s servers the domain belongs to your account. Until you do this, correct nameservers alone show a parking or error page.
Step 4 — Wait for propagation. The registrar publishes the change within minutes, but resolvers worldwide cache the old answer until it expires — typically a few hours, up to 24. Track it at whatsmydns.net (select NS record type); do not judge by your own browser alone, since your devices cache DNS too.
Method 2 — Keep your DNS, point an A record at Hostinger
Use this when you want your DNS to stay where it is — the classic case is Cloudflare, where people want to keep the proxy, firewall, and analytics. It also suits anyone with complex existing records (lots of subdomains, third-party email) who does not want to rebuild the whole zone.
Step 1 — Get your Hostinger server IP. hPanel → Hosting → Plan details → copy the server IP address.
Step 2 — Edit the A records at your current DNS host. Find the existing A records for @ (root) and www and change their values to your Hostinger IP. If they do not exist, create them. Leave every other record — MX, TXT, subdomains — exactly as it is.
Step 3 — Add the domain in hPanel. Same as Method 1, Step 3: Domains → Add Domain. This step is required regardless of method.
Step 4 — Wait for propagation. A-record changes propagate under the same rules (hours, up to 24), governed by the records’ TTL. If you can, lower the TTL to 300 seconds a day before making the change.
Cloudflare-specific note: if the record is proxied (orange cloud), visitors hit Cloudflare first — that is fine and keeps the proxy working, but “DNS only” (grey cloud) is better while diagnosing problems, because it removes a layer. Also note that SSL in hPanel installs normally either way; just make sure Cloudflare’s SSL mode is “Full (strict)” once the Hostinger certificate is active to avoid redirect loops.
Nameserver vs A-record: which should you pick?
- Pick nameservers if you want the simplest setup, one-click email mailboxes, and Hostinger’s DNS editor for future changes. Downside: you rebuild any existing records in Hostinger’s editor.
- Pick the A record if you use Cloudflare’s proxy/firewall, have intricate existing DNS, or run email elsewhere and do not want to touch it. Downside: DNS lives in two places, and Hostinger’s email auto-setup will not apply.
You can switch methods later — it is just another DNS change — so do not agonize. Most first-time site owners should take the nameserver route.
Email warning: read before you switch nameservers
This is the one that bites people. If your domain currently receives email somewhere (Google Workspace, Microsoft 365, your old host’s mail), those MX records live in your current DNS zone. Switching nameservers to Hostinger abandons that zone — and with it, your MX records — so incoming mail silently stops. Before switching: note down every MX, TXT (SPF/DKIM), and related record, and recreate them in Hostinger’s DNS editor (Domains → DNS / Nameservers → DNS records) right after the nameserver change. Or set up Hostinger mailboxes, which publishes correct records automatically — but only if you actually want Hostinger to handle the mail. The A-record method avoids this entirely, since your DNS zone never moves.
Troubleshooting
“It has been over 24 hours and the site does not load.” Verify both halves independently: at the registrar, confirm only Hostinger’s two nameservers are set (no stragglers); in hPanel, confirm the domain appears under Domains. Check whatsmydns.net — if most of the world shows Hostinger but you do not, it is your local cache: try mobile data or flush DNS.
“I see my old website.” Stale cache at your end or a mixed nameserver set at the registrar. Re-check the registrar for leftover old nameservers first.
“My registrar will not let me change nameservers.” Some registrars (notably Cloudflare Registrar) require you to keep their nameservers — that is exactly what Method 2 exists for. Others block changes while the domain is within 60 days of registration or transfer (ICANN rule affects transfers, but a few registrars also freeze nameserver edits) — in that case use the A-record method until the window passes.
“SSL installation fails.” Install the certificate only after the domain resolves to Hostinger over plain HTTP. Certificate authorities must reach your server to validate the domain; pre-propagation attempts fail and you will just have to retry.
FAQ
Do I have to transfer my domain to Hostinger to use their hosting?
No. Transferring changes who bills you for the domain renewal; connecting only points the domain at Hostinger’s servers. Keep the domain wherever it is cheapest or most convenient and use one of the two methods above.
How long does connecting an external domain take?
The hands-on work takes about ten minutes. DNS propagation takes a few hours typically, up to 24 hours worldwide. Start the process a day before any launch.
Will changing nameservers break my email?
It will if your MX records live in the old DNS zone and you do not recreate them. Copy all mail-related records before switching, or use the A-record method to leave DNS untouched.
Can I use Cloudflare with Hostinger?
Yes — it is a popular combination. Keep Cloudflare’s nameservers and use the A-record method (Method 2), with the Cloudflare proxy on for the CDN/firewall benefits. Set Cloudflare’s SSL mode to “Full (strict)” after installing Hostinger’s free certificate.
Next steps
Once the domain resolves, install the free SSL certificate and force HTTPS so visitors get the secure version. If you registered the domain at Hostinger itself rather than externally, the flow is even shorter — see connecting a domain to Hostinger for the nameserver basics. And if email is next on the list, connecting Hostinger email to Gmail picks up right where DNS leaves off.