SaaS provider adding CF is causing Error 1000: DNS points to prohibited IP

Hi there. Our SaaS provider is adding CF to it’s solution, but we host our DNS in CF. I can’t seem to find a way to avoid the Error 1000 and yet still keep our DNS in CF, because I want to retain some controls and use it for other subdomains.

I can’t stop them adding CF, and have a month to figure this out. Any suggestions?

Who is the SaaS Provider?

The likely problem is that the SaaS provider is telling you that you can use https://yourname.saasprovider.com, and you want a custom domain like https://mydomain.com? A regular Cloudflare account cannot have a hostname and certificate active for somebody else’s domain, so they are not offering that service.

If they are a SaaS provider, they should be using Cloudflares SSL for SaaS offering, which provides the necessary functionality for your provider to offer vanity domains with https.

1 Like

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