# Domain change (DNS)

**URL:** <https://community.kinsta.com/t/domain-change-dns/5986>\
**Category:** Questions\
**Created:** [February 16, 2026, 3:29pm UTC](https://community.kinsta.com/t/domain-change-dns/5986 "2026-02-16T15:29:00Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Jason](https://avatars.discourse-cdn.com/v4/letter/j/dc4da7/32.png) [@Jason](https://community.kinsta.com/u/Jason)\
**Post date:** [February 16, 2026, 3:29pm UTC](https://community.kinsta.com/t/domain-change-dns/5986/1 "2026-02-16T15:29:00Z")

</div>

Planned domain migration to Kinsta + Cloudflare — sanity check

We’re preparing to move from a legacy platform to a new WooCommerce build hosted on Kinsta.

The site is currently running on [titanrings.co.uk](http://titanrings.co.uk) (staging/test). The live domain will be [titanjewellery.co.uk](http://titanjewellery.co.uk). We’re a few weeks from launch and planning the DNS switch via Cloudflare.

I’d appreciate a quick sense check on a few points:

1. Domain swap at Kinsta  
Once DNS is pointed to Kinsta, is the correct approach simply:  
• Add live domain in MyKinsta  
• Update/set primary domain  
• Run database search/replace

2. Wordfence 2FA  
Is 2FA tied to the domain, URLs, or user/session data?  
Any lockout risk during the domain change?

3. Cloudflare  
Safe to keep existing Cloudflare Pro and just repoint DNS to Kinsta?

4. Email (Host-IT)  
Email remains hosted externally with Host-IT.  
As long as MX records stay untouched at Cloudflare, should mail flow remain unaffected?

5. Licences & redirects  
I’m aware some plugin licences will need updating for the live domain.  
We’ll also be implementing 301 redirects from legacy Sellerdeck URLs to the new WooCommerce structure.

6. Pitfalls / checks  
Any known Kinsta / Cloudflare / WooCommerce / Host-IT email pitfalls I should double-check?

Goal is a clean transition without downtime or access issues.

Any advice would be appreciated.

---

<div class="post-metadata">

**Author:** ![jackirish](https://sea2.discourse-cdn.com/flex020/user_avatar/community.kinsta.com/jackirish/32/1361_2.png) [@jackirish](https://community.kinsta.com/u/jackirish)\
**Post date:** [February 16, 2026, 9:56pm UTC](https://community.kinsta.com/t/domain-change-dns/5986/2 "2026-02-16T21:56:30Z")

</div>

Hi Jason! 👋 Welcome to the Kinsta Community.

We have some documentation here on how the DNS process works: [WordPress Hosting - Domains and DNS - Kinsta® Docs](https://kinsta.com/docs/wordpress-hosting/wordpress-domains/)

The DNS process itself is:

- Add the domain to the site in MyKinsta
- Verify the domain (this creates the necessary networking piece in our Cloudflare configuration, as well as generating the SSL certificate)
- Set the domain as the primary domain (which includes the search-and-replace)
- _Then_ point the domain, when all the rest is done

That will minimize downtime by ensuring the domain is in place with the necessary network configuration and certificates before pointing the domain.

With regards to Wordfence 2FA, the plugin may need to be deactivated temporarily if it is not working after the move. I believe whether or not it is domain-specific is dependent on its internal settings. If you require assistance with logging in, and are unable to deactivate the plugin via SFTP or [through MyKinsta](https://kinsta.com/docs/wordpress-hosting/wordpress-plugins-themes/wordpress-manage-plugins-themes/#update-activate-or-deactivate-multiple-plugins-or-themes), please contact our Support team: [Support - Contact Support - Kinsta® Docs](https://kinsta.com/docs/support/contact-support/)

It is perfectly save to keep your existing Cloudflare account and simply point it to the site here at Kinsta. Please note that there is a specific DNS setup for these instances though; instead of an A record pointing to an IP address, it will be a CNAME record pointing to **`<sitename>.hosting.kinsta.cloud`**.

As long as the MX records remain untouched, mail flow should remain the same, with one caveat: if you are sending transactional mail through the site itself (such as password resets, or order confirmations), you may need to add

> include:relay.kinstamailservice.com

to your SPF record to allow those emails to be sent/received properly.

Most redirects can be implemented directly in MyKinsta: [WordPress Hosting - Redirects - Kinsta® Docs](https://kinsta.com/docs/wordpress-hosting/redirect-rules/) However if you have any where they are not working, or if you’re not sure, please contact our Support team.

If you do have any questions during any of those other processes as well, please don’t hesitate to contact our team 🙂

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex020/uploads/kinsta/original/2X/8/80f8c4e56fecc02327a0964e6bf63a716483529f.png) [@system](https://community.kinsta.com/u/system)\
**Post date:** [April 30, 2026, 2:59pm UTC](https://community.kinsta.com/t/domain-change-dns/5986/3 "2026-04-30T14:59:04Z")

</div>

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.
