How to Point a Domain to Your Hosting (DNS Guide)

Two ways to connect a domain — nameservers vs A record

Two routes — pick by where you want DNS managed:

1. Nameservers (the common way) — at your registrar, replace the nameservers with your host's (cPanel → General Information shows them, e.g. ns1/ns2.webji.in); your host then serves all DNS records automatically.
2. A record (the surgical way) — keep DNS at the registrar and add one A record: name @ (root), value your server's IP from cPanel's General Information panel.
3. Pick A-record when — email must stay at Zoho or Google while only the website moves.
4. Wait for propagation — TTL governs the cache; expect minutes to 48 hours.
5. Verify — whatsmydns.net for the A record, then open the site.

Registrar-side steps are identical everywhere — see the change nameservers guide, and the domain registration India hub for where domains live.

Finding your nameservers and IP in cPanel

On nameservers (ns1/ns2), the honest summary is that defaults matter more than brand names — a well-set budget plan outranks a mis-tuned premium one. WebJi® documents its defaults openly and adjusts them per ticket when workloads need it.

Changing nameservers at your registrar

Set the nameservers at the registrar, then edit records only in the DNS host those nameservers point at. Editing the other panel does nothing. A website and its mail can use different hosts: the A record sends the site, MX sends the mail.

The A-record route — keeping email at Zoho or Google

The A-record route — keeping email at Zoho or Google. Do the change this heading names on one site first, then check it in a private browser window or in the mail client, depending on the topic. Change one setting at a time, and undo it if the result is wrong before you try the next. If you want the Jaipur desk to look with you, email support@webji.services — that mailbox is staffed 24/7 in Hindi and English. Phone +91 141 4941811 is business hours only.

TTL and propagation — what to expect

TTL is how long a resolver may cache a DNS answer. After an edit, people who cached the old record keep it until that timer ends, so the change can look instant for you and old everywhere else. Drop the TTL a day before a migration, make the change, and raise the TTL once you have confirmed the new target.

Fixing 'site not loading' after pointing

If the site still does not load after pointing, verify in this order. Check whatsmydns.net for the A record: if it shows the old IP, propagation is simply unfinished — wait, or lower TTL and re-check. If it shows the new IP but the browser fails, clear local DNS (ipconfig /flushdns) and try incognito.

If it resolves but shows the wrong site, the document root is the problem — the domain may be an alias or parked rather than the account's primary. If it shows a hosting default page, the vhost is set but content sits elsewhere — check the document root path in cPanel. SSL errors after pointing are a separate, easily-fixed layer: issue the certificate on the new server once DNS is live. Each symptom names its own fix; nothing here requires a ticket.

Pointing www and subdomains

Pointing www and subdomains. Do the change this heading names on one site first, then check it in a private browser window or in the mail client, depending on the topic. Change one setting at a time, and undo it if the result is wrong before you try the next. If you want the Jaipur desk to look with you, email support@webji.services — that mailbox is staffed 24/7 in Hindi and English. Phone +91 141 4941811 is business hours only.