THE MANAGEMENT | Cloudflare setup support
The client got in touch after changing their Webflow account: the server that had always connected would no longer connect. We started work on feel, on the condition that we would refund in full if it did not work out. The cause was a DNS setup that could not hold TXT records, so we used a CNAME instead.

THE MANAGEMENT | Cloudflare setup support
After a change of Webflow account left the client unable to connect to their server, we introduced Cloudflare and brought the domain back to stable operation.
Under the condition that we would refund in full if it did not work out, we rebuilt the DNS configuration from scratch and restored the connection safely and reliably.
Background
THE MANAGEMENT had originally used a Japanese registrar and run their Webflow site via Xserver.
When they changed their Webflow account, however, the server that had connected without trouble until then was no longer recognized, and domain verification broke.
On checking the DNS configuration, we found an environment that did not support TXT records, which meant SSL verification and the Webflow connection settings could not complete correctly.
Approach
Webharu redesigned the structure of the DNS settings and routed the domain through Cloudflare, making flexible record management possible. We switched to a design that passes the verification information with a CNAME in place of a TXT record, and re-ran domain verification on the Webflow side.
We then disabled Cloudflare’s proxy so that the SSL certificate could be issued over a direct connection. With that, both DNS verification and SSL communication were restored to a stable state.
Scope
• New Cloudflare account setup and DNS migration
• Email sending and receiving set up on Cloudflare
• A CNAME-based alternative configuration for an environment without TXT support
• Webflow domain reconnection and SSL verification support
• Proxy settings and cache consistency optimization
What we focused on
Domain connection problems arise not only from configuration mistakes but from differences in what an environment supports. On this project we achieved stable operation by working around that constraint technically. Introducing Cloudflare has since improved both the freedom of DNS management and security performance, making the operational foundation of the Webflow site more robust.
And even with the risk of a full-refund guarantee in place, we saw the work through from implementation to verification.
In closing
In this engagement we bridged three different systems — Webflow, Xserver and Cloudflare — and solved a structural problem at the DNS level. Webharu handles not only production but the redesign of web infrastructure, including operations, connectivity and maintenance.
We will keep supporting clients in building a more stable web environment out of the trouble that starts the conversation.
Your site, the same way.
Start by telling us where things stand.
Production only, care only, or taking over care partway through: we handle all three.