Nameservers vs A Records: Know the Difference
When beginners ask how to point domain to hosting, what they really need is a short DNS lesson first. Your domain name is just a label; DNS records tell the internet which server answers when someone types it. There are two ways to make that connection, and picking the right one saves you a headache later.
Changing nameservers hands control of your DNS to Hostinger. You tell your registrar to use Hostinger’s nameservers, and from then on every DNS record (website, email, subdomains) is managed inside hPanel. This is the simplest route and the one Hostinger recommends for standard websites.
Adding an A record is the surgical option. You keep your DNS exactly where it is (at your registrar or a service like Cloudflare) and add one record that aims your domain at your hosting server’s IP address. This is better for VPS users and for anyone who wants email or other services to stay put. Our domain registration guide covers where domains and DNS live in the first place.
Method 1: Change Your Nameservers (Simplest for Beginners)
This is the method to use if you want Hostinger to handle everything and you are not running email somewhere else.
- Find your nameservers in hPanel. Log in, open your hosting plan, and look for the nameserver or account details section. Most accounts show ns1.hostinger.com and ns2.hostinger.com. Domains parked in hPanel may instead show ns1.dns-parking.com and ns2.dns-parking.com. Copy the exact pair your own panel shows (checked 13 Oct 2026).
- Log in at your domain registrar, the company where you bought the domain.
- Open the nameserver or DNS settings for the domain, choose custom nameservers, paste both values, and save.
- Wait for propagation. Do not keep re-saving settings while you wait; that only restarts the clock.
Nameservers must be typed exactly as shown. A single-character typo is the most common reason this method fails, so copy and paste rather than typing from memory.
Method 2: Keep Your Registrar’s DNS and Point an A Record
Use this method if you run a VPS, host your email elsewhere, or simply want to keep managing DNS at your registrar.
- Find your server’s IP address. In hPanel, open your hosting plan’s details page; the server IP is listed with your account information.
- Open your registrar’s DNS zone editor and add an A record with host @ pointing to that IP address.
- Add a second record for www. Either another A record for www pointing to the same IP, or a CNAME record for www pointing to your domain name. Skipping www is one of the most common mistakes; without it, the www version of your site will not load.
- Set the TTL to 3600 or lower so future changes spread faster, then save and wait for propagation.
This method leaves your MX and other records untouched, which is exactly why it is the safer choice when email lives somewhere else. It also works well on Hostinger VPS plans, where you manage the server yourself.
Propagation: How Long It Takes and How to Check
DNS changes can take up to 24-48 hours to spread across every network on the planet, although most finish within a few hours and many within minutes. The wait is caused by caching at internet providers and DNS resolvers, not by anything Hostinger does slowly.
To check progress, use whatsmydns.net: type your domain, choose A or NS, and watch the results turn green across locations. If the tool shows your new values everywhere but your own browser still shows the old site, your computer has cached the old result; try a different network (phone data works well) or clear your DNS cache. And resist the urge to keep re-saving your settings while waiting. Every change can restart the clock.
Troubleshooting: How to Point Domain to Hosting When It Fails
If a day has passed and nothing works, run through this list before assuming something is broken:
- Typo in a nameserver. Compare what you pasted at the registrar against hPanel character by character.
- Mixed nameserver pairs. Both nameservers must be the new ones; one old and one new creates unpredictable behavior.
- Missing www record. With the A-record method, the bare domain can work while www fails if you forgot the second record.
- Domain expired or registrar lock. An expired domain or an active transfer lock will block DNS changes entirely.
- Very long old TTL. If your previous TTL was set to days, resolvers may legitimately cache the old values for that long.
The fastest diagnosis is whatsmydns.net: it shows what the world actually sees, which tells you whether the problem is your change or just impatience.
Email Warning: Moving Nameservers Can Break Your Inbox
This is the mistake that hurts the most. Changing nameservers moves every DNS record to Hostinger, including the MX records that route your email. If your email is hosted somewhere else, switching nameservers without moving those records will silently kill your inbox: senders get bounces, and you may not notice for days.
Two safe options. Either copy your MX, SPF, DKIM, and DMARC records into Hostinger's DNS zone before you switch nameservers, or skip the nameserver change entirely and use the A-record method, which leaves email records untouched. Our email hosting guide explains how Hostinger's own mail plans handle this if you decide to move email over too.
When Not to Point Your Domain at Hostinger's Nameservers
Hostinger's nameservers are fine for standard websites, but there are honest exceptions. If you need advanced DNS features such as geo-routing, latency-based routing, or complex failover setups, put Cloudflare (or a similar DNS service) in front: point your domain's nameservers there, then aim an A record at your Hostinger server IP. You get the advanced DNS and keep the hosting.
The other exception is scale. If you manage dozens of domains centrally at one registrar, keeping DNS there with A records is simpler than scattering nameservers across hosts. For a single site or a handful of them, the standard nameserver change on a Hostinger web hosting plan is the path of least resistance.
| Approach | You change | DNS managed by | Best for | Watch out for |
|---|---|---|---|---|
| Nameserver change | Nameservers at your registrar | Hostinger | Beginners and standard websites | Email MX records move too; copy them first |
| A record (@ plus www) | Two DNS records at your registrar | Your registrar | VPS users, keeping email separate | You manage every DNS record yourself |
| Parked domain setup | Nameservers at your registrar | Hostinger | Domains parked in hPanel | Use the exact ns1/ns2 pair your panel shows |
| Cloudflare in front | Nameservers to Cloudflare, then an A record | Cloudflare | Advanced DNS needs like geo-routing | Extra hop; records live in Cloudflare |
.com Domain Registration
First year with a 3-year term, paid upfront
Renews at $19.99/yr
- $0.01 for the 1st year
- Renews at $19.99/yr
- Free domain 1st year with yearly hosting plans
FAQ
Most Hostinger accounts use ns1.hostinger.com and ns2.hostinger.com. Domains parked in hPanel may instead show ns1.dns-parking.com and ns2.dns-parking.com. Do not guess: log in to hPanel, open your hosting plan's details, and copy the exact pair shown for your account (checked 13 Oct 2026). Typing a wrong or mixed pair is the most common reason a nameserver change fails.
DNS changes can take up to 24 to 48 hours to spread across every network worldwide, although in practice most changes finish within a few hours and often within minutes. The delay comes from caching at ISPs and DNS resolvers, not from Hostinger. Avoid re-saving your settings while you wait, because each change can restart the propagation clock.
Beginners should change nameservers: it is one change at the registrar and Hostinger then handles every record, including the www version and email, inside hPanel. Choose the A-record method if you run a VPS, host email at another provider, or want to keep DNS management at your registrar. Both routes end at the same place; nameservers are simply harder to get wrong.
It can, yes. Changing nameservers moves every DNS record to Hostinger, including the MX records that route your email. If your email is hosted elsewhere (Google Workspace, Microsoft 365, or another provider), either copy the MX, SPF, DKIM, and DMARC records into Hostinger's DNS zone before switching, or use the A-record method and leave your email records untouched.
Log in to hPanel and open your hosting plan's details or account information page; the server IP address is listed there. You need this IP only for the A-record method. If you are changing nameservers instead, you do not need the IP at all. Copy the IP carefully; a single wrong digit will point your domain at someone else's server.
Yes. Hostinger provisions a free SSL certificate automatically once your domain's DNS resolves to your hosting account. Give it a few hours after propagation completes; the certificate cannot be issued while DNS still points elsewhere. If your site still shows a security warning after a day, check that DNS has fully propagated and then contact Hostinger's 24/7 live chat support.