A subdomain redirect shouldn’t require a workaround. But ours did. And it exposed a deeper problem i
· 1 min read
A subdomain redirect shouldn’t require a workaround. But ours did. And it exposed a deeper problem in our setup.
The redirect worked. Just not the way it should. It relied on an external tool, added an extra hop, and slowed down the flow by a fraction each time.
Most people never notice these delays. But systems do. Funnels do. Users definitely do.
Switching our nameservers to Cloudflare removed the entire chain.
One place to manage DNS. One place to handle the redirect.
And SSL support built in - no extra configuration, no extra tools, no fragile routing.
The redirect became instant. The system became simpler. And the behaviour became consistent.
If something simple needs a workaround, it’s a sign your foundation needs an upgrade.