Ask the client to contact to their former provider and ask them to remove the ‘custom hostname’ they have configured for that hostname on their service.
They were likely using an SSL for SaaS based service and that is overriding the destination. If the former provider can’t or won’t update, [email protected] will need to step in to make a change.
Yes. They said that the name has been removed from their platform. Still struggling. Something appears to be stuck in the CF proxy cache. I’ve got hundreds of domains on the platform, some paid, some free, and over the last decade, I’ve never seen anything like this. When I bypass the proxy, all is fine. My client has reached out to them directly - but their bot says propagation takes time. As most everyone knows, the TTL on CF when using the proxy is near immediate if left at its default. The nameservers were already set - so that shouldn’t be a contributing factor. A second set of nameservers was set with the original nameservers left in place with the proper rules and still, the issue persisted. Again, I’ve never experienced anything like this… It’s crazy.