You have registered a domain and set up hosting, and now the two need to talk to each other so that typing your domain actually loads your website. Connecting a domain to hosting is the step that ties your name to your server — and while it sounds technical, it comes down to one of two straightforward methods, both of which you can do in a few minutes.

This guide explains exactly how to connect a domain to your hosting: the two methods (changing nameservers or pointing an A record), a clear step-by-step for the recommended approach, a Hostinger example, how long it takes, and how to confirm it worked. Whether your domain and hosting are with the same company or different ones, you will know precisely what to do.

The two ways to connect

There are two methods to connect a domain to hosting, and knowing the difference helps you pick the right one. The first is changing your nameservers so your domain points to your host’s nameservers — this hands complete DNS management to your host, which then handles your website, email, and everything else automatically.

The second is pointing an A record: you keep your DNS managed at your registrar and simply add an A record that sends your domain’s traffic to your host’s server IP address. This connects the website while leaving the rest of your DNS where it is.

For most people, the nameserver method is the recommended, simplest choice because the host configures everything in one step. The A-record method is useful when you want to keep managing DNS (like email records) at your registrar. Both achieve the same core goal: making your domain load your site.

Method 1: change your nameservers (recommended)

The nameserver method is the cleanest way to connect a domain, especially for beginners, because your host takes over all DNS configuration. Here is the step-by-step:

• Find your hosting nameservers: log in to your host’s dashboard and locate the nameservers it assigns, usually shown as a pair like ns1.yourhost.com and ns2.yourhost.com. Copy both.
• Log in to your registrar: go to the company where you bought your domain.
• Open nameserver settings: find the Domain List or DNS/Nameserver section and select your domain.
• Choose custom nameservers: select the option to use your own nameservers.
• Paste and save: enter your host’s nameservers into the fields, replacing the old ones, and save.
• Wait for propagation: allow the change to spread worldwide.

Once saved and propagated, your host’s nameservers are authoritative for your domain, so your website loads and you manage all DNS (including email) in the host’s panel. This is why the method is recommended — one change configures everything.

Method 2: point an A record

The A-record method connects your domain while keeping DNS management at your registrar. It is useful if you already manage email or other records there and only want to point the website at your host’s server.

To do it, get your hosting server’s IPv4 address from your host’s control panel. Then log in to your registrar, open the DNS management or zone editor, remove any old conflicting A records, and add a new A record with the host set to @ (for your root domain) and the value set to your host’s IP address. Many setups also add a CNAME for www pointing to the root, or a second A record for www.

Save the record and wait for propagation. Your domain will then resolve to your host’s server while the rest of your DNS stays at your registrar. This method gives you more manual control at the cost of the automatic, one-step configuration the nameserver method provides.

Which method should you choose?

The right method depends on how much you want your host to manage. Here is a quick comparison to guide the choice.

If you want the simplest path and are happy for your host to run your DNS, use nameservers. If you have reasons to keep DNS at your registrar — existing email setup, or you use a separate DNS service — the A record is the better fit. Neither is wrong; they suit different situations.

A Hostinger example

To make it concrete, connecting a domain to Hostinger follows the same pattern. If your domain is registered with Hostinger and you host there too, the connection is often handled automatically — you simply assign the site to the domain in your dashboard and it works, with no manual nameserver entry needed.

If your domain is registered elsewhere, you take Hostinger’s nameservers from your account and enter them at your external registrar using Method 1, or you take Hostinger’s server IP and add an A record at your registrar using Method 2. Either way, you are using the standard methods with Hostinger’s specific values.

This is the advantage of keeping domain and hosting with one provider: the fiddly connection step often disappears entirely. But even with an external domain, pointing it to Hostinger is just the familiar nameserver or A-record process with the values from your Hostinger dashboard.

How long it takes

After you make the change, your domain will not connect instantly everywhere. The update goes through DNS propagation — the delay while it spreads across cached servers worldwide — which typically takes from a few hours up to 48 hours, though many people see it work on their own connection sooner.

During this window it is normal for the site to load on one device or network but not another, as different networks refresh at different times. This is expected behaviour, not a failure, so give it time before assuming something is wrong.

To reduce the wait on a planned change, you can lower your DNS TTL beforehand so caches expire faster. Otherwise, make the change once and be patient — repeatedly editing while waiting only resets the clock and can cause confusion.

How to confirm it worked

Once you have allowed time for propagation, confirm the connection. The simplest check is to visit your domain and see your website load from the new host. If it appears correctly, the connection is live.

You can also verify at the DNS level: a nameserver or NS lookup confirms your domain points to the right nameservers (Method 1), or a DNS lookup confirms your A record resolves to the correct server IP (Method 2). A propagation checker shows how the change is spreading across global locations, which is reassuring during the transition.

If the site still is not loading after full propagation, revisit the basics: are the nameservers or A record entered exactly and completely, did you save at the right place, is your website actually published, and are your domain and hosting active? In most cases, a correctly made connection simply comes online once the caches catch up.

After you connect: keep it working

Once your domain is connected and loading your site, a little maintenance keeps it that way. If you used nameservers, remember that all your DNS now lives in the host’s panel, so any future email setup, subdomains, or verifications are made there. If you used an A record, those changes stay at your registrar, and if you ever change your server’s IP you must update the A record to match.

It is also worth confirming your SSL certificate is active so your site loads securely over HTTPS, and that both the root domain and the www version resolve correctly. A connection that works for example.com but not www.example.com (or vice versa) is a common loose end that a quick check catches.

With the connection made and these small details confirmed, your domain and hosting are reliably linked, and day-to-day you can forget the plumbing entirely and focus on your site.

FAQs

How do I connect a domain to my hosting?

Two ways: change your nameservers at your registrar to your host’s nameservers (recommended — hands all DNS to the host in one step), or add an A record at your registrar pointing your domain to your host’s server IP (keeps DNS at the registrar). After either, wait for propagation and confirm your site loads.

Should I use nameservers or an A record?

Use nameservers for the simplest setup, letting your host manage all DNS including email and subdomains automatically — best for beginners. Use an A record if you want to keep DNS management at your registrar, for example because your email is configured there. Both connect the domain; they differ in where DNS lives.

How do I connect a domain registered elsewhere?

Take your host’s nameservers and enter them at your external registrar (nameserver method), or take your host’s server IP and add an A record at your registrar (A-record method). Both point the external domain to your host. Then wait for propagation and check that your site loads from the new host.

How long until my domain connects to my site?

Usually a few hours, up to 48 hours for full worldwide propagation, though it often works on your own connection sooner. During that window the site may load on some networks before others, which is normal. Lowering your DNS TTL beforehand speeds up a planned change.

My domain isn’t loading my site — why?

Common causes: propagation not finished (wait), nameservers or A record entered incorrectly, changes saved in the wrong place, the website not published yet, or an expired domain/hosting plan. Confirm each is correct and give a proper change time to propagate before concluding there is a deeper problem.

Is it easier if my domain and hosting are with the same company?

Yes. When your domain is registered with the same provider you host with, the connection is often handled automatically — you just assign the site to the domain, with no manual nameserver or A-record entry. That convenience is a common reason people keep domain and hosting together.

The bottom line

Connecting a domain to your hosting is the step that makes typing your name actually load your website, and it comes down to two methods. Changing your nameservers points your domain at your host’s nameservers and hands all DNS management to the host in one step — the recommended, simplest route, especially for beginners. Pointing an A record sends your domain’s traffic to your host’s server IP while keeping DNS at your registrar — useful when you want to manage email or other records there yourself. Both reach the same goal; they differ only in where your DNS lives.

Whichever you choose, the process is quick: get the values from your host (nameservers or server IP), enter them at your registrar, save, and wait for propagation — a few hours up to 48. Then confirm by visiting your site and, if needed, checking with a DNS or propagation lookup. When domain and hosting are with the same provider, like Hostinger, the connection is often automatic. Set it correctly once, be patient through propagation, and your domain and website will be reliably linked.

When you are ready, you can start with Hostinger and use code PROTIPS for the reader discount. Connect a domain to hosting by changing nameservers (host manages all DNS, recommended) or adding an A record to the host’s IP (DNS stays at registrar). Enter values from your host, save, and wait for propagation.