Changing your domain’s nameservers is one of those tasks that sounds intimidating but is actually a short, well-defined procedure — and it is the key step in connecting a domain to a new host, moving your DNS to a service like a CDN, or consolidating where your DNS is managed. Done in the right order, it is smooth and low-risk; done carelessly, it can briefly knock your site or email offline. This guide makes sure you do it the right way.

You will learn exactly why and when to change nameservers, where the change is made (at your registrar, not your host), a clear step-by-step process, what to prepare beforehand so nothing breaks, how long the change takes, and how to verify it worked. Follow along and you will repoint your domain confidently, with minimal or no downtime.

Why and when to change nameservers

The most common reason to change nameservers is to point your domain at a new host that will manage your DNS. When you build your site with a hosting company different from your registrar, updating the nameservers to the host’s tells the internet to look to that host for your domain’s settings.

You might also change nameservers to move your DNS to a specialised service — such as a content delivery network or a dedicated DNS provider — that offers performance, security, or management benefits. In that case you point your nameservers at that service, which then controls your records.

If your domain and hosting are already with the same provider, you usually never need to change nameservers, since the defaults point correctly. So this is mainly a task for connecting separate services or consolidating control — an occasional change, not a routine one.

Where you change nameservers: the registrar

This is the point that confuses many people: nameservers are changed at your registrar — the company where you bought and manage the domain — not at your hosting company. Your host provides the nameserver addresses you should use, but the actual change is made in your registrar’s control panel.

The logic is that the registrar controls the domain’s fundamental settings, including which nameservers it points to. Your host cannot change that for you; it can only tell you what to enter. So the workflow is: get the nameservers from your host, then log in to your registrar to apply them.

If your registrar and host happen to be the same company, this distinction blurs and it may be handled automatically. But whenever they are separate, remember: the host supplies the nameservers, and the registrar is where you set them.

What to prepare before you change

A little preparation prevents downtime. The most important step is to recreate your DNS records at the new provider before switching, so that the moment your domain points there, everything it needs is already in place. Otherwise, there can be a gap where your site or email stops working.

Specifically, make sure the new nameservers already have your website’s A record (pointing to the correct server), your email’s MX and related TXT records, and any other records your domain relies on. Setting these up in advance means the transition is seamless rather than a scramble.

It is also wise to note your current settings before changing anything, so you have a record to fall back on if needed. And if you can, plan the change for a low-traffic period, giving any brief transition the least possible impact on visitors and email.

The step-by-step process

With your records prepared, the change itself is straightforward and the same in principle at every registrar:

• Log in to the company where you bought your domain (your registrar).
• Find your domain in your list or portfolio and select it.
• Locate the section named Nameservers, DNS, or Manage DNS.
• Choose custom nameservers (or the option to enter your own).
• Enter the new nameservers your host or DNS provider gave you — typically a primary and a secondary, such as ns1.example.com and ns2.example.com.
• Save or update to apply the change.
• Wait for propagation and then verify the domain resolves to the new destination.

That is the whole procedure. Enter every nameserver your provider supplies (usually two or more), remove the old ones, and save. From there it is a matter of letting the change propagate and confirming it worked.

A Hostinger example

To make it concrete, imagine pointing a domain to Hostinger for hosting. Hostinger provides its nameservers (a primary and secondary set) in your account. You would take those, log in to wherever your domain is registered, open the nameserver settings, select custom nameservers, and paste in Hostinger’s nameservers.

If your domain is registered with Hostinger as well, this is even simpler — pointing the domain to Hostinger’s hosting can be handled within one dashboard, often automatically. When the registrar is elsewhere, you copy Hostinger’s nameservers into that registrar’s panel.

Either way, once the nameservers are set to Hostinger’s and propagation completes, your domain’s DNS is managed in Hostinger’s panel, where your website and email records live. It is the same universal process, simply using Hostinger’s specific nameserver addresses.

How long it takes and downtime

After you save the change, nameserver updates usually start taking effect within a few minutes, but complete propagation across the whole internet can take up to 48 hours. During this window, the change reaches different networks at different times, so results may be inconsistent for a while.

There is a real downtime consideration here: because changing nameservers moves DNS control entirely to the new provider, any records that are not set up there will not work until you add them. This is precisely why preparing your records in advance matters — with them in place, visitors experience little or no interruption as the change propagates.

If you did prepare properly, most users will transition smoothly, with perhaps a brief period where some see the old setup and others the new. Avoid re-editing during propagation, and simply let the change settle across the world’s networks.

How to verify the change worked

Once you have allowed time for propagation, confirm the change took effect. The simplest check is to visit your website and see that it loads from the new host, and to test that your email still sends and receives correctly — the two things most affected by a nameserver change.

You can also look up your domain’s nameservers via your registrar or a public lookup tool to confirm they now show the new provider’s nameservers rather than the old ones. A DNS propagation checker can show how the change is spreading across different global locations, which is reassuring during the transition.

If something is not working after full propagation, revisit the basics: are the nameservers entered exactly and completely, and are all necessary DNS records present at the new provider? In most cases, a correctly prepared change simply comes online cleanly once the caches around the world catch up.

FAQs

How do I change my nameservers?

Log in to your registrar (where you bought the domain), select the domain, find the Nameservers or DNS section, choose custom nameservers, enter the new ones your host or DNS provider gave you (usually a primary and secondary), remove the old ones, and save. Then wait for propagation and verify your site and email work at the new destination.

Where do I change nameservers — at my host or registrar?

Always at your registrar, the company where you bought and manage the domain — never at your host. The host supplies the nameserver addresses to use, but the registrar is where you actually enter them, because it controls the domain’s fundamental settings. If your registrar and host are the same company, it may be handled automatically.

How long does a nameserver change take?

Changes usually start taking effect within a few minutes, but full propagation across the internet can take up to 48 hours. During that window, different networks update at different times, so results may be inconsistent for a while. Preparing your DNS records at the new provider beforehand keeps the transition smooth as it propagates.

Will changing nameservers cause downtime?

It can if you are not prepared, because changing nameservers moves DNS control entirely to the new provider — any records not set up there will not work. The fix is to recreate your website, email, and other records at the new provider before switching. With records in place, visitors experience little or no interruption during propagation.

How do I point my domain to a new host?

Get the host’s nameservers from your account, log in to your registrar, open the nameserver settings, choose custom nameservers, and enter the host’s nameservers, removing the old ones. Before switching, set up your DNS records at the new host so nothing breaks. After saving, allow propagation and confirm your site and email work.

How do I know if my nameserver change worked?

Check that your website loads from the new host and that email still works, since those are most affected. Look up your domain’s nameservers via your registrar or a public tool to confirm they show the new provider, and use a propagation checker to watch the change spread globally. A well-prepared change usually comes online cleanly after propagation.

The bottom line

Changing nameservers is the key step in pointing your domain at a new host or moving your DNS to another service, and the golden rule is where it happens: always at your registrar, where you manage the domain, never at your host — the host merely supplies the nameserver addresses to enter. The process itself is short: log in to the registrar, find the nameserver settings, choose custom nameservers, enter the complete set your provider gave you, remove the old ones, and save.

The difference between a smooth change and a stressful one is preparation. Because switching nameservers hands over DNS control entirely, you should recreate your website, email, and other records at the new provider first, so everything works the moment the domain points there. After saving, allow up to 48 hours for propagation, avoid re-editing, and then verify by checking that your site loads and email flows, that your nameservers show the new provider, and that a propagation checker confirms the change globally. Prepared properly, repointing your domain is a confident, low-downtime task.

When you are ready, you can start with Hostinger and use code PROTIPS for the reader discount. Change nameservers at your registrar (not your host): select the domain, open nameserver settings, enter the host’s custom nameservers, and save. Recreate your DNS records at the new provider first to avoid downtime.