When you sign up with WPCloud, you need to point your domain to our servers so visitors reach your WordPress site. There are two ways to do this.
Option A (Recommended): Change your nameservers to WPCloud. This hands DNS management over to WPCloud. We manage all DNS records for your domain on Constellix, our DNS provider. This is the simplest option and what we recommend for most clients.
Option B: Keep your current DNS and point an A record. You keep managing your own DNS and add an A record pointing to the IP address WPCloud provides. Choose this if you need to keep your DNS with your current provider (for example, if you use Cloudflare’s proxy or have a complex DNS setup you manage yourself).
Before You Make Any DNS Changes
Your WPCloud hosting account and WordPress site must be set up and ready before you change DNS. If you point your domain before your account is provisioned, the domain will point to nothing and your site will go offline.
Before starting, confirm that:
- Your WPCloud account is active and your site has been set up
- You have your server’s IP address from WPCloud (needed for Option B)
- You have exported or written down any existing DNS records you need to keep, especially MX records for email (Google Workspace, Microsoft 365, etc.), SPF/DKIM/DMARC records, and any third-party verification TXT records
Option A: Changing Nameservers to WPCloud (Constellix)
Set your domain’s nameservers to all six of the following:
ns11.constellix.comns21.constellix.comns31.constellix.comns41.constellix.netns51.constellix.netns61.constellix.net
Note that the first three use .com and the last three use .net. Add all six if your registrar allows it. If your registrar only accepts two, use ns11.constellix.com and ns41.constellix.net (one from each group).
After the nameserver change takes effect, WPCloud manages your DNS. If you use a third-party email provider (Google Workspace, Microsoft 365, Zoho, etc.), open a support ticket so we can add your MX and related records to Constellix. Have your existing DNS records on hand so we can recreate them.
Option B: Pointing an A Record
If you are keeping your DNS with your current provider, add or update these records:
A record at the root/apex (@) pointing to the IP address WPCloud provided you.
TXT record at the root (@) for email delivery (SPF): v=spf1 include:relay.mailchannels.net ~all
If you already have an SPF record for another email service, merge the MailChannels include into your existing record. Do not create a second SPF TXT record. DNS only allows one SPF record per domain. For example, if you use Google Workspace, your merged record would be: v=spf1 include:relay.mailchannels.net include:_spf.google.com ~all
For more detail, see Setting up SPF Records for MailChannels Email Authentication.
Do not use a CNAME record at the root domain. A CNAME at the apex conflicts with your NS and SOA records and will break your DNS. Use an A record for the root domain. CNAME records are fine for subdomains like www.
Registrar-Specific Instructions
Below are the steps for common registrars. Registrar interfaces change from time to time, so if the steps below do not match what you see, check your registrar’s help documentation or contact their support.
GoDaddy
Nameservers (Option A): Log in and go to your Domain Portfolio. Select the domain to open Domain Settings. Under Nameservers, select “I’ll use my own nameservers,” enter the six Constellix nameservers, and save. If Domain Protection is enabled, you will need to verify your identity (SMS or authenticator code).
A/TXT records (Option B): In Domain Settings, go to DNS, then Manage DNS. Click Add New Record. For the A record, set Host to @ and Points To to your WPCloud IP. For the TXT record, set Host to @ and Value to your SPF record.
Watch for: If the domain is locked, unlock it in Domain Settings before changing nameservers. If the domain uses external nameservers, GoDaddy’s DNS page is not authoritative; make changes where DNS is actually hosted.
Support: godaddy.com/help | Phone: 1-480-505-8877
Namecheap
Nameservers (Option A): Log in, go to Domain List, and click Manage next to your domain. In the Nameservers section, select Custom DNS from the dropdown, enter the Constellix nameservers, and click the green checkmark to save.
A/TXT records (Option B): From Domain List, click Manage, then go to Advanced DNS. Under Host Records, click Add New Record. Choose A Record, set Host to @, and enter your WPCloud IP. For TXT, add a new TXT Record with Host @ and Value set to your SPF record.
Watch for: Namecheap allows up to five nameserver entries. If the domain is pointed to Namecheap hosting, DNS may be managed in cPanel rather than Advanced DNS.
Support: namecheap.com/support | Live chat 24/7
Squarespace (Formerly Google Domains)
Google Domains was acquired by Squarespace. If you had a Google Domains account, your domain is now managed through Squarespace.
Nameservers (Option A): Log in at domains.squarespace.com. Select your domain, find the Nameservers section, select “Use custom nameservers,” enter the Constellix nameservers, and save.
A/TXT records (Option B): In the domain settings, go to DNS Settings (or DNS Connect) and add an A record and TXT record.
Watch for: Squarespace distinguishes between “Nameserver Connect” and “DNS Connect,” and where you edit records depends on which model the domain is using. If you use Google Workspace email through Squarespace, switching nameservers will disconnect it. Consider Option B instead, or re-add your MX records after the switch. Some domains migrated from Google Domains may still show Google’s nameservers (ns-cloud-e1 through e4.googledomains.com) as a migration artifact; update them in Squarespace’s dashboard.
Support: support.squarespace.com
Cloudflare (as Registrar)
If Cloudflare is your registrar, your domain uses Cloudflare’s nameservers by default. Switching to external nameservers (Option A) is restricted on most Cloudflare plans. For WPCloud clients with Cloudflare-registered domains, Option B is the recommended approach.
A/TXT records (Option B): In the Cloudflare dashboard, go to DNS, then Records. Click Add Record. For the A record, set Name to @ and IPv4 Address to your WPCloud IP. Set the Proxy Status to “DNS only” (grey cloud). The orange cloud (Cloudflare proxy) must be off for the A record to point directly to WPCloud. For the TXT record, add a new record with Name @ and Content set to your SPF record.
Watch for: If DNSSEC is enabled, you may need to disable it before making nameserver changes and re-enable it after. The Cloudflare proxy (orange cloud) on your A record will route traffic through Cloudflare instead of directly to WPCloud, which can cause SSL and caching conflicts.
Support: community.cloudflare.com | developers.cloudflare.com/dns
Hover
Nameservers (Option A): Log in at hover.com, go to Domains, select your domain, click Nameservers (or Edit), switch to custom nameservers, enter the Constellix nameservers, and save.
A/TXT records (Option B): In domain settings, go to Records and add an A record (Name @, Content: your WPCloud IP) and a TXT record (Name @, Content: your SPF record). Hover only allows DNS record management when the domain uses Hover’s own nameservers. If you switch to Constellix, record management moves to Constellix.
Watch for: Hover says nameserver changes can take 24 to 48 hours. Hover is a Tucows reseller. If your domain is registered directly with Tucows rather than through Hover, you may need to manage it through your Tucows account.
Support: support.hover.com | Email: support@hover.com
Tucows / OpenSRS
Tucows/OpenSRS is a registrar backend. Most end users manage their domains through a reseller (Hover, or another Tucows reseller) and should follow their reseller’s instructions. If you have a direct OpenSRS account, nameserver changes are made in the Reseller Control Panel under Bulk Actions or the individual domain’s settings.
Watch for: OpenSRS DNS/Zone management features require OpenSRS nameservers. If you switch to Constellix, you manage records in Constellix, not OpenSRS. End users typically contact their reseller for support, not Tucows directly.
Support: support.opensrs.com (for resellers; end users should contact their reseller)
WHC.ca (Web Hosting Canada)
Nameservers (Option A): Log in to the WHC Client Area at clients.whc.ca. Go to Domains, then My Domains. Click Manage on your domain and update the nameservers to the Constellix nameservers.
A/TXT records (Option B): In the Client Area, go to Domains, click the domain, then the gear icon (top right), and open the Advanced DNS Manager. Click Add Record and create your A and TXT records.
Watch for: WHC’s DNS record management is in the Advanced DNS Manager. Once nameservers move to Constellix, the WHC panel is no longer authoritative; manage records at Constellix (or through WPCloud support).
Support: clients.whc.ca | Phone: 1-866-976-9835
Webnames.ca
Nameservers (Option A): Log in to your Webnames.ca account. Go to Account, then Manage Domains. Click the domain, and under Domain Actions, click Manage under Name Servers. Enter the Constellix nameservers.
A/TXT records (Option B): In the DNS interface, click Add Record. For an apex A record, leave the hostname field empty (this represents the root domain). For the TXT record, enter your SPF value and save.
Watch for: A hostname with a CNAME cannot also have other record types (A, MX, etc.), which matters at the root. Webnames supports DNSSEC; if enabled, disable it before switching nameservers.
Support: webnames.ca/help | Phone: 1-866-976-9835
Other Registrars (Name.com, Dynadot, ca.domains, etc.)
The process is the same at any registrar: find the nameserver or DNS settings for your domain, replace the existing nameservers with the six Constellix nameservers listed above (Option A), or add an A record and SPF TXT record (Option B). If you cannot find these settings, contact your registrar’s support team. They handle DNS configuration questions regularly.
DNS Propagation: What to Expect
After making a DNS change, it takes time for the update to spread across the internet. This is called propagation.
Typical timeline: Most nameserver and A record changes take effect within 15 minutes to 4 hours. In rare cases (long TTL values, conservative ISPs), it can take up to 24 to 48 hours.
During propagation: Some visitors may see your site on the old server while others see it on WPCloud. This is normal. The site may also show SSL certificate warnings until WPCloud’s system provisions your certificate, which happens automatically once DNS resolves to our server. If you see SSL warnings, wait 15 to 30 minutes and try again.
How to check propagation: Use whatsmydns.net to see how your domain resolves from locations around the world. Enter your domain and check whether the returned IP matches the WPCloud IP you were given. Once most locations show the correct IP, propagation is complete.
Tip: If you know you will be changing DNS soon, reduce the TTL (Time to Live) on your existing DNS records to 300 seconds (5 minutes) a day or two in advance. This ensures the old records expire quickly and the change propagates faster.
Common Mistakes
Changing DNS before your WPCloud account is ready. Your domain will point to nothing. Always confirm with WPCloud that your site is set up before touching DNS.
Losing email records when switching nameservers. If you use Google Workspace, Microsoft 365, or another email provider, their MX records (and often SPF/DKIM records) must exist at your new DNS provider. Before switching to Constellix, export or write down all your existing DNS records. After the switch, open a WPCloud support ticket so we can add them.
Using a CNAME at the root domain. The root/apex domain (e.g., example.com) needs an A record, not a CNAME. A CNAME at the apex conflicts with the NS and SOA records that must exist there. Use A records for the root and CNAME for subdomains.
Leaving registrar default records in place. Some registrars add parking pages, URL redirects, or placeholder records by default. These can conflict with your WPCloud site. Remove them after pointing your domain.
Forgetting to disable registrar lock. Some registrars have a domain lock (or transfer lock) that prevents nameserver changes from taking effect. The change appears to save but does not propagate. Disable the lock before changing nameservers and re-enable it afterwards.
Leaving Cloudflare proxy enabled. If you use Cloudflare for DNS (Option B), make sure the A record is set to “DNS only” (grey cloud), not “Proxied” (orange cloud). The proxy routes traffic through Cloudflare instead of directly to WPCloud and can cause SSL and caching conflicts.
A Note for .ca Domains
DNS changes for .ca domains work the same way as any other domain. Changes are made at your registrar, not at CIRA (the Canadian Internet Registration Authority). CIRA manages the .ca registry but does not handle day-to-day DNS configuration. There is no special delay for .ca nameserver changes beyond normal propagation times.
Need Help?
If you are unsure how to change your DNS settings, or if something does not look right after making the change, open a support ticket at support.wpcloud.ca. Let us know your domain name, which registrar you use, and whether you chose Option A or Option B. We will walk you through it.
Leave a Reply