You registered the domain, bought the hosting, typed the name into the browser… and your site didn’t show. That’s normal: domain and hosting are two separate services, and the domain doesn’t know where your site lives until you tell it. “Connecting a domain to hosting” means telling the Domain Name System: whoever asks for this name, send them to that server. This guide explains the two ways and when to choose each, the steps on cPanel hosting, a VPS and DNS Console, and how to make sure the connection worked.
01Where the world reads your site’s address
Every domain points to that keep its records. When a visitor types chai-alrasheed.com, the site of Al Rasheed Tea House, their device asks these servers: what’s this name’s address? They answer with an holding the IP address of the server that carries the site. From the same servers, the world’s mail learns where to deliver your messages, through MX records.
So the connection happens in one of two places: at the domain’s registrar, where you choose its name servers, or inside the domain’s zone itself, where you write its records. Hence the two ways.
02Way one: switch the name servers to your hosting’s
The simpler of the two: you make your hosting’s name servers responsible for the domain, and the hosting creates the records the site and mail need by itself.
- 01Find your hosting’s name servers: They’re in your hosting account’s details, or ask technical support through a ticket from the client area.
- 02Open the domain’s settings at its registrar: If the domain is registered with Illevante, you manage domains and DNS records in the client area.
- 03Put the hosting’s servers in place of the current ones: Remove all the old ones and don’t mix two providers’ servers: if the servers the extension delegates to differ from the ones the domain’s zone declares, each side answers something different.
- 04Add the domain in the hosting panel: In cPanel the main domain comes with the account; you add other domains under “Domains”.
- 05Follow the propagation: Check the domain with the DNS propagation checker on Illevante’s site until every point answers with the new servers.
And if you register a new domain and hosting with Illevante, you need none of these steps: the domain connects to the hosting automatically, with no manual name server setup.
03Way two: keep DNS where it is and point an A record
Choose it when your domain has records working somewhere else that you don’t want to move, such as mail on another service, or when you want the domain’s zone to stay put and change only the hosting.
- 01Find your server’s IP address: in cPanel it shows in the account information as Shared IP Address; on a VPS it’s the server’s address in its panel.
- 02In the domain’s zone, create an A record for the name @, the domain itself, with that address as its value.
- 03Create a record for www: either an A with the same address, or a pointing at the main domain.
- 04If your server has an IPv6 address, add an AAAA record with it too.
- 05Leave the MX records alone if your mail is on another service; they’re what deliver your messages there.
| Type | Name | Value | What it does |
|---|---|---|---|
| A | @ | The server’s IP address | Takes the domain itself to the site |
| CNAME | www | chai-alrasheed.com | Makes the www form follow the domain |
| MX | @ | Your mail server and its priority | Delivers mail, and stays as it is |
04On a VPS: the domain arrives, the site is up to you
An A record brings the visitor to your VPS, but the server itself has to know what to serve for that name. After the record, add the domain to the web server it runs, or to the control panel you installed, then issue it an SSL certificate. If you’d rather a control panel took these steps off your hands, cPanel, Plesk and ISPmanager licenses are available for your server from Illevante.
05DNS apart from your hosting: DNS Console
If you have several domains on different hosting, or want your records to stay in one place however often you change hosting, manage them in DNS Console: add the domain and its records or apply a template to it, then set the name servers ns5.illevante.cloud and ns6.illevante.cloud at the registrar, and its zone answers from the platform. The platform supports thirteen record types, from A, AAAA, CNAME, MX and TXT to CAA and DS.
06How long it takes, and how to know it worked
A change doesn’t reach the whole world at once: resolvers that saved the old answer keep it until its runs out. So one visitor in Baghdad may see your new site while another in Basra sees the old one for hours.
Follow it with the DNS propagation checker on Illevante’s site: it asks about the domain from 14 cities, including Dubai, Riyadh and Cairo, and 5 public resolvers, compares each answer with the authoritative name servers, and adds a domain health report. And once the domain reaches our cPanel hosting, AutoSSL issues it an SSL certificate automatically, which can take a few minutes after the connection.
- ProblemThe site opens without www but not with it
- FixAdd a record for www: an A with the server’s address or a CNAME to the domain.
- ProblemYou changed name servers and mail stopped
- FixAdd the MX and other records at the new destination before the change.
- ProblemYou still see the old site
- FixWait for the old TTL to run out, and check the domain with the propagation tool rather than your own device alone.
- ProblemThe domain doesn’t work at all after registration
- FixMake sure it has name servers at its registrar; nothing propagates before they’re added.
- ProblemA certificate warning right after connecting
- FixWait a few minutes for AutoSSL to issue the certificate, then check the site with the SSL checker.
Connecting is a step you take once, but doing it in order spares you a site and mail outage: prepare the records first, then change the servers, then follow the propagation to the end.
