My Domain Isn't Resolving (DNS Hosting)

If your domain isn't loading your site or mail isn't arriving after setting up DNS Hosting, work through these checks in order.

1. Check the nameserver status in your panel

Open your DNS management panel — the banner at the top shows a live check of your domain's actual public nameservers, not a cached or assumed state.

• "Not pointed here yet" — your registrar still shows your old nameservers, or the change hasn't propagated. Double-check you edited the nameservers for the right domain at your registrar, and give it more time (up to ~24-48 hours in rare cases).
• "Partially switched" — some resolvers see our nameservers, others still see your old provider. This is normal mid-propagation; it should resolve to "correctly pointed" on its own.
• "Correctly pointed" — nameservers are fine; the problem is with a specific record instead (see below).

2. Confirm the record actually exists

Open Manage DNS records and check that the record you expect is actually there, with the right name and content. A record for www won't make the bare domain (@) work, and vice versa — you typically want both if you expect people to reach your site either way.

3. Check the TTL

If you changed a record recently, the old value may still be cached by your own ISP's resolver or your browser until the previous TTL expires. Try from a different network, or use a third-party DNS checker to see what's actually being served to the wider internet right now, before assuming the record itself is wrong.

4. For mail specifically: check your MX record points somewhere real

An MX record needs to point at an actual mail server hostname, which itself needs a working A/AAAA record — an MX record pointing at a hostname with no A record behind it will never deliver mail. If you're using RepublicNodes Mailbox Hosting, the MX value you need is shown on your mailbox service's own page.

Still stuck?

Contact support with your domain name and which record isn't behaving as expected — we can check the zone directly on our end and confirm whether it's a propagation issue or a record configuration issue.