Nameservers in one paragraph
What are nameservers? They are the servers that answer the internet’s most basic question about your domain: where is this website? Every domain has nameservers assigned at its registrar, and those servers hold the DNS records, the A records, MX records, and others, that map your domain to actual servers. When you buy hosting somewhere new, you point your domain there by changing its nameservers to your host’s addresses. From that moment, the host’s nameservers are authoritative for your domain: anyone asking where your site lives gets the answer from them. It is a simple handoff with one quirk that confuses everyone the first time: changes take time to spread across the world, a process called propagation, so your site may work for you before it works for everyone. Understand that, and nameservers stop being mysterious (checked 14 Oct 2026).
How DNS turns names into addresses
Computers do not understand domain names; they route by IP address. DNS, the Domain Name System, is the phone book that translates between the two. When someone types your domain, their device asks a chain of servers: the root servers point to the registry for your extension, the registry points to your domain’s nameservers, and your nameservers return the actual records, like the A record holding your server’s IP. Your browser then connects to that IP. Nameservers sit in the middle of this chain as the authoritative source for your domain’s records. That is why changing nameservers is such a powerful move: it redirects the entire chain to a new authority in one step. It is also why the change is not instant; DNS resolvers worldwide cache old answers until they expire, which is the propagation delay everyone warns you about. Typical propagation is a few hours, occasionally up to 48.
Nameservers vs DNS records: the difference
Beginners mix these up constantly, so here is the clean distinction. Nameservers decide who answers DNS questions for your domain. DNS records are the answers themselves: the A record points your domain to a server IP, the CNAME aliases one name to another, MX records route your email, and TXT records handle verification and email security like SPF. You can change where your site is hosted in two ways. Option one: change the nameservers to your new host, handing them full DNS control; simplest for beginners, since the host then manages all records for you. Option two: keep your current nameservers and just edit the A record to the new server’s IP; more control, but you manage DNS yourself. Most people should use option one. One warning: moving nameservers can break email if your MX records do not move correctly, so check email before and after. Domain basics are covered further at Hostinger domain registration.
What are nameservers at Hostinger, and how to check yours
So what are nameservers in Hostinger’s world specifically? Hostinger uses nameservers like ns1.hostinger.com and ns2.hostinger.com for hosting accounts, and parked domains may show ns1/ns2.dns-parking.com; always confirm the exact pair in your hPanel under the hosting plan’s details, since the right values depend on your account. To change nameservers, log in to wherever your domain is registered, find the nameserver or DNS settings, switch to custom nameservers, paste in the two addresses from hPanel, and save. Then wait: check progress with a propagation tool like whatsmydns.net rather than refreshing hopefully. Do not change anything else during propagation, and keep your old hosting active for a few days so nothing goes dark mid-move. If email stops after the switch, your MX records did not carry over; add them in hPanel’s DNS zone editor. The whole job takes ten minutes of clicking plus patience, and it is the standard way to connect any domain to Hostinger web hosting.
Mistakes that cause real downtime
Nameserver changes are simple, but three mistakes cause most outages. First, changing nameservers and cancelling old hosting on the same day: during propagation some visitors still reach the old server, so keep it alive for several days. Second, forgetting email: MX records live in DNS, so a nameserver move without migrated mail records silently kills incoming email; businesses discover this on Monday morning. Third, typing the nameserver addresses wrong, a single character breaks everything and the error gives you no useful message. Prevention is boring: copy-paste instead of typing, screenshot your old DNS records before changing anything, and verify with a propagation checker before declaring victory. If something breaks, the fix is usually to correct the record and wait; DNS problems are almost never fixed by changing more things faster. Patience is a technical skill here. For current deals while you set things up, check the Hostinger coupon code page (checked 14 Oct 2026).
When pointing at Hostinger is not the right move
Changing nameservers to Hostinger is right when Hostinger hosts your site and you want the simplest DNS setup. It is the wrong move in a few cases. If your DNS is managed somewhere with features you rely on, like Cloudflare's proxying and firewall, keep your nameservers there and point an A record at Hostinger instead; you keep the features and the site still loads from Hostinger. If your email lives with Google Workspace or Microsoft 365 with carefully tuned records, double-check every record survives the move, or again, keep DNS where it is. And if you need Windows hosting or a dedicated server, Hostinger cannot provide them at all, so do not point anything at Hostinger until the hosting question is settled. Nameservers are just the signposts; make sure the destination is right first (checked 14 Oct 2026).
| Task | Where to do it | Difficulty | Propagation |
|---|---|---|---|
| Change nameservers | Domain registrar | Easy | Up to 24-48 hours |
| Edit A record | Current DNS host | Easy | Minutes to hours |
| Add MX for email | DNS zone editor | Medium | Minutes to hours |
| Verify the switch | whatsmydns.net | Easy | - |
| Fix email after move | hPanel DNS editor | Medium | Minutes to hours |
.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
Nameservers are the DNS servers that hold your domain's records and tell the internet where your website and email live. Changing them to your host's addresses is how you point a domain at new hosting. They are the authoritative source browsers consult through the DNS chain.
DNS resolvers around the world cache old records until they expire, so your change spreads gradually rather than instantly. Most changes are visible within a few hours, but the safe quoted window is 24 to 48 hours. Lowering TTL values a day before the change can speed things up.
Nameservers decide who answers DNS questions for your domain; DNS records are the answers themselves, like the A record pointing to your server IP or MX records routing email. You change nameservers to move authority to a new host; you edit records to change individual services.
Usually ns1.hostinger.com and ns2.hostinger.com for hosting accounts, though parked domains may use a dns-parking.com variant. Always confirm the exact pair inside your hPanel under your hosting plan details, since the correct values depend on your account.
Yes, if your MX records do not move correctly. When you change nameservers, email routing moves with DNS, so verify your MX, SPF, and DKIM records in the new DNS zone before and after the switch. Test by sending yourself an email from an outside account.
Yes. Instead of changing nameservers, keep your current DNS and just update the A record to point at the new server's IP. You keep full DNS control and only the website moves. This is the preferred method for people comfortable managing DNS records themselves.