Adding a domain with multiple wildcard A records to Kinsta requires a few extra DNS steps compared to a standard domain add. This is because Kinsta uses Cloudflare for domain verification, and wildcard A records can interfere with that process. The steps below walk through how to get the domain verified and correctly pointed so it works with your Kinsta site, including what to check if something goes wrong.
When Do You Need These Steps?
These steps apply only when your domain is configured with wildcard A records – for example, a DNS setup where *.example.com points to multiple IP addresses simultaneously. This configuration is common in DNS failover setups, round-robin load balancing, and some CDN configurations.
If your domain uses standard A records (one IP per hostname), follow the normal domain-adding process in MyKinsta. Kinsta will tell you if your domain has multiple wildcard A records and that you need to follow these additional steps.
What Is a Multiple IP Domain?
A multiple IP domain uses wildcard A records that point a hostname (such as *.example.com) to more than one IP address. This distributes traffic across multiple servers and is used for DNS-level load balancing, geo-routing, and failover protection. When Kinsta tries to verify a domain configured this way, the standard verification flow can fail because the wildcard records conflict with the custom hostname check Cloudflare needs. The steps below work around that.
In a DNS control panel, a wildcard multi-IP setup looks something like this:
- Type: A | Host: * | Value: 192.0.2.1 | TTL: 300
- Type: A | Host: * | Value: 192.0.2.2 | TTL: 300
- Type: A | Host: * | Value: 192.0.2.3 | TTL: 300
If your DNS panel shows multiple A records with a wildcard host pointing to different IPs, you are in this scenario and need the steps below.
Step 1 – Create Static A Records for the Domain
Before starting verification in MyKinsta, go to your DNS provider and create static, non-wildcard A records for the domain you want to add to Kinsta. These records should point to the same IP addresses used by your existing wildcard A records.
For example, if your wildcard A record points to three IPs, create an explicit A record for your root domain – and for the www subdomain if relevant – pointing to each of those same IPs. This gives Kinsta and Cloudflare a consistent, predictable target to verify against.
Allow 5 to 10 minutes for the new records to propagate before moving to Step 2. You can use a DNS checker tool to confirm the static A records are resolving before starting the MyKinsta verification flow.
Step 2 – Verify the Domain in MyKinsta
Once the static A records are in place, go to MyKinsta and start the domain-add process. In the Verify Domain modal, click Next. Kinsta will prompt you to add one or more TXT records to confirm domain ownership.
The TXT record is formatted as follows:
Type: TXT
Hostname: _cf-custom-hostname.example.com (replace with your actual domain)
Value: a unique UUID string provided by Kinsta in the modal
Add this record at your DNS provider. Once added, return to MyKinsta and click Okay I’ve Done It. Kinsta verifies the record in the background – this can take a few minutes to several hours depending on your DNS provider’s propagation speed.
Step 3 – Point the Domain to Kinsta
Once Kinsta confirms your domain is verified, the dashboard displays a Point Domain button. Click it to reveal your Site IP Address – the Cloudflare edge IP that routes traffic through Cloudflare before it reaches your Kinsta server.
Go back to your DNS provider and remove the static A records you created in Step 1. You do not need to remove the existing wildcard A records – if those are serving other purposes, they can stay in place without affecting the Kinsta setup.
Step 4 – Add the Final A Record
Create a new A record for the domain or subdomain pointing to the Kinsta Site IP Address shown in the modal. Once DNS propagates, you will see a green checkmark next to the domain in your MyKinsta Domains section, confirming it is correctly pointed and active through Kinsta’s Cloudflare network.
Adding Subdomains to Kinsta: Standard Process
If you want to add a subdomain to a Kinsta site and your DNS does not use wildcard A records, the process is simpler than the steps above. In MyKinsta, navigate to Sites > Your Site > Domains and click Add Domain. Enter the subdomain (for example, shop.example.com or blog.example.com), and Kinsta walks you through standard TXT record verification followed by A record pointing.
Common reasons to add a subdomain on Kinsta include running a staging version of your site under a subdomain, hosting a separate section of a business at a different subdomain, or pointing multiple country-code domains to the same WordPress install.
One thing worth checking after adding a subdomain: make sure your WordPress address and site URL settings match the domain you want as the canonical. If you add www.example.com as an additional domain but your site URL is still set to example.com (non-www), visitors going to www will be redirected rather than served directly.
What to Do If the Green Checkmark Never Appears
If you have completed all four steps but the green checkmark is not showing in MyKinsta after 24 hours, work through this checklist:
- Check that the TXT record is still present – Some DNS providers auto-delete verification records. Confirm the _cf-custom-hostname TXT record is still in your DNS panel.
- Check that the final A record points to the correct IP – The IP shown in the Point Domain modal is a Cloudflare edge IP, not a standard Kinsta server IP. Verify you used that specific IP, not an older one.
- Remove conflicting records – Any CNAME, AAAA, or other A records pointing to different addresses on the same hostname can prevent the checkmark from appearing. Leave only the A record pointing to the Kinsta site IP.
- Contact Kinsta support – If DNS is correct and the domain is still not confirming, the issue may be at the Cloudflare custom hostname layer. Kinsta support can check the Cloudflare verification status directly from their side.
Kinsta DNS Settings Reference
Here is a quick reference for the DNS records you need when pointing a domain to Kinsta. These values apply whether you are managing DNS at your registrar, through Cloudflare, or through another DNS provider.
| Record Type | Name/Host | Value/Points To | Notes |
|---|---|---|---|
| A | @ (root domain) | Kinsta IP address | Found in MyKinsta under Sites > Domains. Use the primary IP assigned to your site. |
| A | www | Kinsta IP address | Points www to the same Kinsta IP as the root domain. |
| CNAME | www | yourdomain.com | Alternative to an A record for www. Use this if your DNS provider does not support ANAME/ALIAS records at the root. |
| TXT | @ or specific subdomain | Kinsta verification string | Required for domain verification in MyKinsta. Kinsta provides the exact value during the Add Domain process. |
| A | subdomain | Kinsta IP address | For subdomains (e.g. blog.yourdomain.com), add a separate A record pointing to the same IP. |
If you are using Cloudflare in front of Kinsta, set the proxy status to DNS Only (grey cloud) for the A record during initial verification. You can re-enable the orange cloud proxy after Kinsta has verified the domain and issued the SSL certificate. Running Cloudflare’s proxy before SSL is issued causes a verification failure.
For the full Cloudflare integration setup, see our guide on using Cloudflare as a DNS provider.
Final Word: Adding a Domain with Multiple IP Addresses on Kinsta
If Kinsta flags your domain as using multiple wildcard A records, the four steps above are the correct path. The extra verification steps exist because Kinsta routes all domains through Cloudflare’s custom hostname system, which needs a clean A record to verify against. Once the static records are in place for verification, then removed once the domain is pointed, the setup works the same as any other Kinsta domain. Allow up to 24 hours for DNS propagation and check MyKinsta for the green confirmation checkmark before testing the live site. Once your domain is correctly pointed, the next step is to enable Kinsta’s built-in Cloudflare integration for CDN caching, SSL, and DDoS protection. If you are handing the site over to a client, see our guide on how to transfer company ownership on Kinsta once all domains are configured.
