Vidensdatabase

If you've registered your domain elsewhere (Namecheap, GoDaddy, Cloudflare Registrar, etc.) you have two ways to point it at your ipxcore hosting account: changing nameservers, or adding individual DNS records. This article explains both, and when to use which.

Method 1: Change nameservers (recommended)

This is the simplest option and is what we recommend for most customers. Log in to your domain registrar's control panel and set the nameservers to:

• all1.dnsroundrobin.net
• all2.dnsroundrobin.net

That's it. ipxcore now controls all DNS for your domain — A records, MX records, TXT records, everything is managed in your cPanel's Zone Editor.

Method 2: Use an A record (keep DNS at registrar)

If you want to keep DNS management at your registrar (often the case if you're using Cloudflare proxying or registrar-specific features), add an A record instead:

• Type: A
• Host/Name: @ (the apex domain) and a separate one for www
• Value: the IP address shown in your cPanel welcome email (or in cPanel's "General Information" sidebar)
• TTL: 3600 (or "Automatic")

You'll need to maintain MX records, SPF, and any other DNS records yourself at the registrar.

A vs. CNAME — what's the difference?

• A record: maps a hostname to an IPv4 address. Use this for the apex domain (yourdomain.com) and any subdomain that points directly to a server.
• AAAA record: same as A but for IPv6 addresses.
• CNAME record: maps a hostname to another hostname. Common use: www.yourdomain.com as a CNAME pointing to yourdomain.com. CNAMEs cannot be used on the apex domain (RFC 1912 restriction).
• MX record: tells the world where to deliver mail for the domain. Defaults to mail.yourdomain.com on our servers.
• TXT record: arbitrary text. Used for SPF, DKIM, DMARC, domain ownership verification, and many other purposes.

How to verify your DNS is correct

From a terminal:

$ dig yourdomain.com +short
192.0.2.10
$ dig www.yourdomain.com +short
yourdomain.com.
192.0.2.10

The IP returned should match your ipxcore server's IP. From a browser, you can use whatsmydns.net to see how DNS is propagating across global resolvers.

How long does DNS propagation take?

Most ISPs honor the TTL on your DNS records (typically 1 hour). Some larger ISPs and corporate networks cache for longer — up to 24 hours in rare cases. We recommend not cancelling your old hosting account until at least 48 hours after a DNS change.

Common pitfalls

• Old A record cached at registrar: after switching nameservers, double-check that the registrar's old DNS panel doesn't still have stale A records — some panels merge their old DNS settings with the new nameservers in confusing ways.
• Cloudflare orange-cloud: if your domain proxies through Cloudflare, the IP that visitors see is Cloudflare's, not ipxcore's. That's expected. Use grey-cloud (DNS only) for any record where you need direct IP access (mail, FTP, etc.).
• www subdomain missing: set up both the apex (@) and www records, otherwise www.yourdomain.com won't resolve.
• SSL not issuing: if AutoSSL keeps failing after DNS change, it's usually because validation traffic still hits the old host. Wait 30 minutes and re-run AutoSSL. Detail in our CSF article.