Pointing your domain to WHC hosting (nameservers + DNS)

When you buy hosting from us, your website lives on our servers — but visitors only reach it once your domain points there. There are two ways to do that. Pick the one that matches your situation.

Option A: Full nameserver delegation (recommended)

This is the simplest setup: you tell your domain registrar “use WHC’s nameservers”, and we handle every DNS record for you.

When to use it: You bought your domain from us, or your domain is at another registrar but you don’t have specialised DNS needs (no Cloudflare, no external services managing records).

How to do it:

1. Log in to your domain registrar
2. Find the nameserver settings (sometimes called “DNS servers” or “name servers”)
3. Replace whatever’s there with:
   • ns1.rocoder.com
   • ns2.rocoder.com
4. Save

That’s it. Within 1–24 hours (usually closer to 1) your domain resolves to our servers, and we manage all the records — A, AAAA, MX, TXT — automatically based on your hosting setup.

If your domain is registered with us, this is set up by default; you don’t need to do anything.

Option B: Individual DNS records (advanced)

Keep your nameservers wherever they are (often Cloudflare or your registrar’s DNS) and create individual records pointing at our servers.

When to use it: You’re using Cloudflare for CDN/security, or you have other services that need DNS records (Google Workspace, MX for a separate mail provider, etc.).

Records to create:

Type	Host	Value
A	@	(your hosting IP — we’ll tell you)
A	www	(your hosting IP)
MX	@	(your mail server — we’ll tell you)
TXT	@	(SPF record — we’ll provide)
TXT	_dmarc	(DMARC record — we’ll provide)

Your welcome email lists the exact IP address and mail server hostname for your account. If you’ve misplaced it, open a ticket and we’ll send the details.

TXT records for email are important. Without proper SPF and DMARC, your outbound email gets flagged as spam.

Cloudflare-specific notes

If you’re proxying through Cloudflare (the orange cloud icon), be aware:

• Cloudflare’s IP shows up instead of ours — that’s expected
• SSL certs should be set to “Full (strict)” mode, not “Flexible”
• Some firewall rules can block legitimate traffic — review them after the switch
• Don’t proxy the MX record; mail must hit our servers directly

Checking if it worked

Use dig from a terminal or an online tool like dnschecker.org:

dig yourdomain.com.au A
dig yourdomain.com.au MX
dig yourdomain.com.au NS

The A record should match our server IP. The NS records should match the nameservers you set. Globally, you can check propagation at dnschecker.org — most regions show the new values within an hour or two.

Common issues

• Site loads on temp URL but not on your domain. DNS hasn’t fully propagated yet. Wait 24 hours. If still broken, the records aren’t right — open a ticket.
• Email going to old host. MX record didn’t update or there’s a stale Cloudflare proxy on it.
• “This site can’t be reached” errors. Browser DNS cache. Try a different network or ipconfig /flushdns (Windows) / dscacheutil -flushcache (Mac).

When in doubt, open a ticket with your domain name and what you’ve tried. We’d rather walk you through it than have you guess.