www subdomain is resolving the wrong endpoint, redirect or page rules not honored. Trace tool says hostname is not in my account?
What steps have you taken to resolve the issue?
Hello,
https://www.successacademy.com subdomain is not resolving properly. It is pointed to a very old third party service that we no longer use. I attempted to create a Page Rule and a Redirect Rule and it still resolves an endpoint we phased out over a year ago.
While I was looking at the Trace tool, I noticed that running it against https://successacademy.com give back the proper trace I setup. However, when I use the Trace tool against “https://www.successacademy.com” the Trace tool errors out stating “There was an error and your trace could not be performed. Please try another URL or amend your configurations: hostname does not belong to your account”. It’s as if someone hijacked the subdomain from another Cloudflare account?
Why would it say that for the subdomain? Can anyone from cloudflare help?
What feature, service or problem is this related to?
DNS not responding/updating
What are the steps to reproduce the issue?
1.) Change “www” record from DNS only to Proxied
2.) Loads wrong endpoint
3.) Add Redirect Rule and/or Page Rule
4.) Loads wrong endpoint
This would mean your Cloudflare DNS for www has A/AAAA records that point to a host that also uses Cloudflare. In that case requests do not pass through your account (as the trace says) and instead pass through the host’s account. From headers, it looks like you may be using Kajabi… https://cf.sjr.dev/tools/check?4385bc89410e41bc9d8943c2e30d62b7#connection-server-https
Right, we moved this domain elsewhere but there are other services still tied to the domain such as Google Workspaces. The apex record is being redirected based off the second Page Rule. For whatever reason, the first Page Rule is ignored when visiting the “www” subdomain.
As the trace and I said above, if your host is also using Cloudflare and you are pointing at the host using A/AAAA records then requests aren’t passing through your Cloudflare account so your settings won’t have any effect. The host needs to use Cloudflare for SaaS and you need to use their CNAME as your DNS record for your Cloudflare account settings to work.
