This hostname is currently pointing to a service provider blocking my own redirects

What is the name of the domain?

cognitivetechnology.ca

What is the issue you’re encountering

I want to use my redirect rules, however everytime I point my domain to websites.durablesites.com, it takes over the redirect. Cloudflare tells me: This hostname is currently pointing to a service provider. Changing the DNS target will reroute traffic to the newly defined origin and will disable any settings or services that are currently being utilized through the provider. How can I have it self managed? I even tried pointing direct to their IP address, but CF detects that and bypasses any of my local settings. I don’t see any way on my side to disable this which seems at odds with me being able to manage my own sites…

What steps have you taken to resolve the issue?

I’ve tried pointing directly to the IP addresses, CNAMEs, and CF detects the service provider each time.

Hello,

Reviewing the DNS record, I am able to see the A record is not proxied.
Could you kindly toggle icon to orang cloud ?

Cloudflare tells me: This hostname is currently pointing to a service provider.

Besides, kindly provide us the screenshot of this error that is displaying from your end

Kindly review this link regarding redirect rule :

Thank you

1 Like

Here’s screenshots of the entire configuration. The redirect used to work with my old webhost. But it appears durable.com is somehow tied directly into cloudflare? And I can’t disable it, so in a sense they have direct control over my configuration…I dont’ want that.

Check with Durable if you are ok to use a CNAME instead of A records. According to this it is websites.durable.co as here…

(but check with them as I’m not sure).

Using the CNAME for www and the apex domain should allow you to use O2O so requests pass through your account first, if they are using Cloudflare for SaaS and not some legacy Cloudflare custom setup.

1 Like

That O2O is exactly what I wanted…but it just wasn’t behaving that way. I originally had the CNAME set as you suggest (I’ll put it back now). But the redirects were not taking place. It’s good to know O2O exists…So at least I now know it’s supposed to work that way. I’ll test it out one more time and respond back. Thank you!!

All will depend on if they are using the current Cloudflare-for-SaaS (where O2O works fine) or if they have some custom or legacy setup which may/may not have been reworked to work with O2O as in these…

Let us know how you get on as it will help others.

Ok it’s all setup like you say.

The DNS response now with the CNAMEs + Proxy =
|www.cognitivetechnology.ca. 300|IN|A|172.67.188.115|
|www.cognitivetechnology.ca. 300|IN|A|104.21.8.115|

When I go to www.cognitivetechnology.ca/meeting, it gives a 404. So I guess they must be using legacy?

Is there any way for me to enforce it to use my setup, then simply proxy to theirs like any normal website? Can I dissalow them from hijacking my CF setup? Is there a hidden setting somewhere?

This topic was automatically closed after 15 days. New replies are no longer allowed.