You bought your domain at one company and your hosting at another — a completely normal, common setup — and now you need the two to work together. Pointing an “external” domain (one registered away from your host) to your hosting is a routine task, and once you know the two methods, it takes just a few minutes at your registrar.

This guide explains exactly how to point an external domain to your host: what “external” means here, the two methods (nameservers or DNS records), step-by-step instructions for each, when to choose which, a Hostinger example, and how to verify it worked. By the end, connecting a domain and hosting that live at different companies will feel simple.

What “external domain” means

An external domain is simply a domain registered at one company (your registrar) while your website is hosted at a different company (your host). For example, you might have bought yourdomain.com at one registrar years ago, and now you want to host your site with a separate hosting provider. That domain is “external” to the host.

This is a very common situation and nothing to worry about — domains and hosting are separate services, and mixing providers is perfectly normal. It just means the connection between them is not automatic the way it is when both are with the same company, so you set it up yourself.

The good news is that pointing an external domain to your host is a well-worn, straightforward process. You will make the change at your registrar (where the domain lives), using nameservers or DNS values that your host provides. That is the whole idea: tell the domain, at its home, to send traffic to your host.

Method 1: change nameservers (recommended)

The recommended way to point an external domain is to change its nameservers to your host’s. This hands complete DNS management to your hosting provider, which then configures your website, email, and everything else automatically. Here is the process:

First, find your hosting provider’s nameservers in your hosting dashboard or welcome email — usually a pair like ns1.yourhost.com and ns2.yourhost.com. Then log in to your domain registrar (where you bought the domain), go to the DNS Management or Nameserver Settings for your domain, and replace the existing nameservers with your host’s custom nameservers. Save the change.

After saving, allow time for propagation. Once complete, your host’s nameservers are authoritative for the domain, so your site loads and you manage all DNS in the host’s panel. This is the simplest method because a single change configures the whole connection.

Method 2: update A records and CNAME

The alternative is to keep your registrar’s DNS zone active and point traffic with records instead. Use this method if you want to continue managing DNS (such as existing email records) at your registrar while hosting the website elsewhere.

To do it, find your hosting server’s IP address in your hosting control panel. Then log in to your registrar and open the DNS editor. Create or update an A record pointing @ (your root domain) to your host’s IP address, and typically add a CNAME record for www pointing to your root domain, so both yourdomain.com and www.yourdomain.com resolve correctly.

Save the records and wait for propagation. Your website will then load from your host while the rest of your DNS stays under your control at the registrar. This method trades the one-step simplicity of nameservers for the ability to keep managing your DNS where it already is.

Which method to choose

The choice comes down to where you want your DNS managed. Here is a quick comparison for pointing an external domain.

Choose nameservers if you want the host to handle everything with minimal effort — the usual pick. Choose A record + CNAME if you have an existing DNS or email setup at your registrar that you want to preserve. Both reliably point the external domain to your host; they differ only in who manages DNS afterward.

A Hostinger example

Pointing an external domain to Hostinger uses these exact methods with Hostinger’s values. For the nameserver method, you copy Hostinger’s nameservers from your account and paste them into your external registrar’s nameserver settings, replacing the old ones. Hostinger then manages your DNS.

For the record method, you take your Hostinger server’s IP address and add an A record at your external registrar pointing @ to that IP, plus a www CNAME to your root domain. Your DNS stays at the registrar while the site loads from Hostinger.

Hostinger provides both the nameservers and the server IP clearly in your dashboard, so whichever method you prefer, you are simply copying the right value across to your registrar. The process is identical to connecting any external domain — only the specific values are Hostinger’s.

How long it takes

Like any DNS change, pointing an external domain does not take effect instantly. It propagates over time — typically a few hours, up to 48 hours for full worldwide coverage — as networks refresh their cached DNS. You may see the site load on one connection before another during this window, which is normal.

To make a planned change propagate faster, lower your DNS TTL a day or two beforehand so caches expire sooner. And to avoid any downtime, if you are using the nameserver method, make sure your website and email records are ready at the host before you switch, so everything resolves the moment the change lands.

Beyond that, patience is the main requirement. Make the change once, then let it settle rather than re-editing, which only restarts propagation. In the vast majority of cases the connection simply completes on its own within a day or two.

How to verify it worked

After propagation, confirm the connection by visiting your domain — if your website loads from the host, the pointing worked. For the nameserver method, a nameserver lookup should show your host’s nameservers; for the record method, a DNS lookup should show your A record resolving to the correct server IP.

If email is involved and you used the nameserver method, check that mail still flows, since DNS control moved to the host — you may need to confirm your MX records are set there. If you used the record method, your email records at the registrar should be untouched and working as before.

Should the site not load after full propagation, recheck that the nameservers or records are entered exactly and completely, saved at the registrar, and that the website is published at the host. A correctly pointed external domain reliably comes online once the world’s caches have refreshed.

Preparing to avoid downtime

A little preparation makes pointing an external domain seamless. If you use the nameserver method, remember that it hands all DNS to the host — so before switching, recreate any records you rely on (especially email MX records) at the host, so nothing breaks the moment the domain points there.

If you use the A-record method, you avoid that concern because your DNS zone stays at the registrar untouched except for the records you add. This is actually a reason some people prefer it when they have a working email setup they do not want to disturb.

Either way, plan the change for a quiet period if the site is live and important, note your current settings before changing anything as a fallback, and confirm the destination is ready. With the records in place at the right provider, the transition is smooth and your visitors barely notice — the domain simply starts resolving to your host.

FAQs

How do I point an external domain to my host?

At your registrar, either change the domain’s nameservers to your host’s nameservers (recommended — hands all DNS to the host), or add an A record pointing @ to your host’s server IP plus a www CNAME (keeps DNS at the registrar). Get the values from your host, save at your registrar, and wait for propagation.

Where do I make the change — registrar or host?

At your registrar, where the domain is registered. Your host provides the values (nameservers or server IP), but you enter them at the registrar because it controls the domain’s fundamental settings. If your registrar and host are the same company, the connection is often handled automatically instead.

Should I use nameservers or A records for an external domain?

Use nameservers to hand all DNS to your host in one step — simplest, and the host manages email and subdomains automatically. Use A records plus a www CNAME if you want to keep DNS management (like existing email) at your registrar. Both point the external domain to your host; they differ in where DNS lives afterward.

Will pointing an external domain cause downtime?

It can with the nameserver method if the host is not ready, because DNS control moves entirely to the host — recreate your website and email records there before switching. The A-record method avoids this since your DNS zone stays at the registrar. Preparing records in advance keeps the transition seamless.

How long does it take to point an external domain?

Usually a few hours, up to 48 hours for full worldwide propagation, though often sooner on your own connection. The site may load on some networks before others during that window, which is normal. Lower your DNS TTL beforehand to speed up a planned change.

How do I know the external domain is pointing correctly?

Visit your domain and confirm your site loads from the host. A nameserver lookup should show your host’s nameservers (nameserver method), or a DNS lookup should show your A record resolving to the host’s IP (record method). A propagation checker confirms the change is spreading across global locations.

The bottom line

Pointing an external domain — one registered away from your host — to your hosting is a routine, few-minute task done at your registrar, using values your host provides. You have two methods: change the domain’s nameservers to your host’s (recommended, since it hands all DNS management to the host and configures your website and email in one step), or add an A record pointing your root domain to the host’s server IP plus a www CNAME (which keeps DNS at your registrar, ideal when you already manage email there). Both reliably connect a domain and hosting that live at different companies.

Whichever you choose, the flow is the same: get the nameservers or server IP from your host, enter them at your registrar, save, and wait for propagation — a few hours up to 48. Prepare your records at the destination first (especially with the nameserver method) to avoid downtime, then verify by visiting your site and checking with a DNS lookup. With a clear dashboard like Hostinger’s providing the values, pointing an external domain is simply a matter of copying the right value to the right place and letting the change propagate.

When you are ready, you can start with Hostinger and use code PROTIPS for the reader discount. Point an external domain at your registrar: change nameservers to your host’s (hands DNS to the host) or add an A record to the host’s IP + www CNAME (DNS stays at registrar). Prepare records first, save, and wait for propagation.