How to Point a Domain to Hosting

What pointing a domain at hosting actually changes

Pointing a domain at hosting changes one of two things: the nameservers your registrar publishes, or the A record inside the zone those nameservers serve. The hosting account itself does not change. The site appears when the domain resolves to the server and that server has a site set up for the name.

A domain name is only a label. Two layers decide where it leads. The registrar holds the delegation, which names the servers that answer for the zone. Those nameservers hold the records: A for an address, CNAME for an alias, MX for mail, TXT for verification.

• Nameserver switch: the host takes the whole zone, and every record moves with it.
• A-record edit: one record changes, and mail, TXT and everything else stays put.
• TTL: how many seconds a resolver may keep the old answer before it asks again.
• Pointing is free and it is not a transfer. The domain stays with its registrar.

Find your nameservers and server IP in cPanel

Both values come from the hosting side, never from the registrar. The welcome email lists the two nameservers and the server IP address. In cPanel, the General Information panel on the right shows the shared IP address. On a VPS the address sits in the provider email or the server control panel.

1. Search the mailbox for the hosting welcome email. Copy the two nameserver hostnames and the IPv4 address into a note.
2. Log in to cPanel and read General Information for the shared IP, to confirm the address is still the one in the email.
3. If neither is handy, email support@webji.services with the domain name and ask for the nameservers and IP. Support replies 24/7 in Hindi and English.

You need both only if you are unsure which route you will take. Route 1 uses the two hostnames, route 2 uses the IPv4 address.

Route 1: change the nameservers at the registrar

This is the usual route for a new site. The host becomes the authority for the zone, so every record you add later lives in cPanel. Do it in this order and the change takes one edit plus one wait.

1. Sign in at the registrar where the domain was bought. This is not the hosting login, even when one company sold you both.
2. Open the domain list, select the domain, and find the DNS or nameserver section.
3. Choose custom nameservers and replace both entries with the pair from the welcome email. A primary and a backup are required; one alone is a single point of failure.
4. Save. Approve the confirmation email the registrar may send, or the change stays pending.
5. Wait for the old TTL, then check with dig before you change anything else.

If the mailbox for this domain lives at Zoho, Google or Microsoft 365, stop here and use route 2. Moving nameservers moves the MX records with them, and mail stops the moment the new zone has none.

Route 2: keep DNS where it is and change the A record

This route leaves the zone at the registrar, at Cloudflare, or wherever it already answers, and rewrites a single record. It is the right choice when mail or a verification record must not move.

1. Open DNS management at the provider that currently answers for the domain, not at the new host.
2. Find the A record for the bare domain and change the value to the server IP. If TTL is editable, set 300 while you test.
3. Add an A record or a CNAME for www pointing at the bare domain.
4. Leave MX and TXT untouched, then save.
5. Check the answer with dig, and send yourself a test mail to prove the mailbox still works.

Check the change with dig before you blame propagation

Propagation is not a mystery event. It is the old TTL running down. Ask a public resolver and the host's own nameserver, and compare the two answers.

• dig +short yourdomain.com A shows what your own resolver returns right now.
• dig +short yourdomain.com NS shows which nameservers the registrar has delegated.
• dig @1.1.1.1 yourdomain.com A asks Cloudflare directly, skipping your local cache.
• dig @ns1.yourhost.com yourdomain.com A asks the host's nameserver, which is the truth once the zone is live.
• On Windows the same test is nslookup yourdomain.com 1.1.1.1.

If the public resolver shows the new IP and your laptop still shows the old page, the change is done and your cache is stale. Flush it with ipconfig /flushdns on Windows, sudo dscacheutil -flushcache on macOS, or sudo resolvectl flush-caches on Linux. Stable records commonly carry a TTL of 3,600 to 14,400 seconds; a record you are about to change should carry 300.

Fix the site that still will not load

Most "not working" reports after a pointing change are not DNS faults. Match the symptom before you edit a record a second time.

The certificate row catches people out. AutoSSL issues a certificate only for names that point at the account, so pointing and issuing happen in that order, not the other way round.

Point www, a subdomain, or a second domain

Every name needs its own record. www is a separate hostname from the bare domain, and a subdomain is a separate hostname again.

• www: a CNAME to the bare domain is the tidy option, and an A record with the same IP also works.
• Subdomain such as shop.yourdomain.com: add the record, then create the domain in cPanel so a site exists for it.
• Second domain on one account: point it by either route, then add it as an addon domain with its own folder.
• Cloudflare in front: keep the proxy switched on only after the origin answers correctly, or you will debug the proxy instead of the host.

WebJi® registers .com and .in domains and keeps the renewal in the same billing panel; prices are on domain registration in India. A domain bought elsewhere does not need to move to work here. The nameserver change walkthrough covers the registrar screens in more detail, and DNS records explained covers what each record type does. For the hosting side of the account, see cPanel hosting.