Each WP Squared site runs on a domain or subdomain. For the site to load, and for its free SSL certificate to be issued, the domain's DNS must point to your WP Squared server. This guide walks through connecting domains, getting HTTPS working and changing a site's domain later.
Before you start
- Access to the WP Squared dashboard from MdmHost dashboard → Services.
- Access to your domain's DNS: at your registrar, at a DNS provider such as Cloudflare, or through MdmHost if we host your DNS.
- The WP Squared server's IP address, shown in your service details or the WP Squared dashboard.
Point the domain
| Record | Name | Value |
|---|---|---|
| A | @ (example.com) | The WP Squared server IP |
| A or CNAME | www | The same IP, or example.com |
| AAAA (optional) | @ and www | The server's IPv6 address, if provided |
Keep MX and other mail records as they are; changing the website's A record does not move email. DNS changes usually take effect within an hour but can take up to 48 hours.
Attach the domain to a site
- When creating a site, choose the domain in the creation form.
- For an existing site, open the site in the WP Squared dashboard and use its domain settings to add or change the domain, where your version offers that option.
- Subdomains such as
shop.example.comneed their own A or CNAME record pointing to the server.
Get SSL issued
WP Squared requests free certificates automatically once the domain resolves to the server. Check the padlock at https://example.com and https://www.example.com. If the certificate is missing after DNS has propagated:
- Confirm both names resolve to the server IP with the IP checker or
dig example.com +short. - Remove CAA records that do not allow the certificate provider.
- If you use Cloudflare, set SSL mode to Full (strict) and avoid rules that block
/.well-known/.
Force HTTPS
In WordPress, make sure Settings → General uses https:// for both addresses. Then ensure visitors on http:// are redirected, either through WP Squared's site settings if available or with an .htaccess redirect. Check for mixed content in the browser console afterwards.
Change a site's domain
- Point the new domain to the server and wait for DNS.
- Change the site's domain in WP Squared, or update Settings → General in WordPress.
- Run a serialisation-safe search and replace from the old to the new URL.
- Add a 301 redirect from the old domain so links and rankings carry over.
Troubleshooting
- Site shows another host's page: DNS still points elsewhere, or your computer caches old DNS.
- Certificate warning on www only: the
wwwrecord is missing. - Redirect loop: Cloudflare in Flexible mode combined with an HTTPS redirect.
- Email stopped after DNS change: MX records were changed or nameservers moved without copying mail records.
Frequently asked questions
Should I change nameservers or just the A record?
Changing only the A records for the website is the least disruptive option when your email and other services are hosted elsewhere. Moving nameservers is simpler when MdmHost should manage all DNS, but copy every existing record (MX, TXT, CNAME) first.
Can one site answer on several domains?
Choose one main domain for the site and redirect the others to it with 301 redirects. Serving identical content on several domains splits search rankings.