Neither domain is on Cloudflare. You’ll ask your host here for further help I am afraid.
Thanks for the prompt response. The root domain is at www.thomashenthorne.com and it is indeed on Cloudflare with Argo.
The 301 redirect in the case of www.390FawnDrive.com is to https://www.thomashenthorne.com/390-fawn-drive-san-anselmo/
Hope this helps.
thomashenthorne.com is, but what’s the issue about that domain? The other two domains are not relevant in this context.
The root domain loads just fine.
The other domains use 301 redirects (permanent forwarding) to pages on that domain. Those redirects are timing out with connection errors. I should put “domains” in quote because the vanity url are not real domains, they just 301 forward to thomashenthorne.com
But that brings us back to the original response, these domains are not on Cloudflare, so you need to discuss this with your host.
If you have a web related issue with a domain on Cloudflare, that’s the right place. Otherwise it is beyond the scope of the forum.
These domains aren’t hosted. They are 301 redirects. There is no host to discuss with.
That redirect still has to come from a server and that’s your host. Point is, these domains are not on Cloudflare, so whatever they are doing Cloudflare is not involved.
Do you have an issue with a domain on Cloudflare?
You’d have to add them here and use the following tutorial:
In that case they’d be hosted by Cloudflare and the redirect would come from there, the question though was why there are intermittent connectivity issues and those are not Cloudflare related but will be something on the current host.
They point to GoDaddy and NameCheap, so those certainly are the source of the problems.
Thanks both for your continued help.
The strange thing is… a flushdns command makes the domain redirect work fine until I do another reload.
The other strange thing is I have been doing this with “dummy” namecheap domains (property addresses forwarding to pages on thomashenthorne.com) for years … hundreds of these. I haven’t changed anything so I’m wondring what has changed.
Namecheap is located in Eastern Europe… I wonder if my geoblocking in Cloudflare on thomashenthorne.com is somehow rejecting the 301 redirect from the dummy domains?
I am afraid, that’s really something to discuss with your host and would be off-topic here for now. Of course you could move these domains to Cloudflare and configure the redirect on Cloudflare’s side, but that would be a whole different subject.
Any current issues are not Cloudflare related and your Cloudflare domain loads fine.
Thank you… I will go back to Namecheap on this. Every entity involved (Go Daddy, Namecheap, WP Engine, Cloudflare) sends me to a different entity so it’s been interesting.
Also I can’t figure out why this happens ONLY on Chrome… and reproduces easily (go to 390FawnDrive.com, it loads, then reload it again, you get error, then flush dns, it loads, etc)… this does not happen in Firefox or Safari. This is super strange.
That’s the point, Cloudflare is not involved
Your Cloudflare domain works fine and the others do not involve Cloudflare. It’s difficult to tell what the issue might be and it could be anything from caches, to DNS and routing or network issues. If your host can’t help you it might be an idea to ask for help in a related forum, such as StackExchange or Reddit.
One last try at this… don’t kill me…
I just ran a ping test on site24x7.com and when I first loaded 390FawnDrive.com it gave normal responses… then it said unreachable and gave the error:
" * The Name Server domain is not reachable from the Internet because there is a firewall or filtering router that is blocking connections to port 53 on this host for both UDP and TCP connections. The firewall configuration must permit connections on this port from any host on the Internet for the DNS to function properly." It also says “The SOA record for the zone is required to be present in the primary Name Server and is not found. This usually means that the zone file is not setup properly in the primary Name Server host. It may also be due to any of the following reasons.”
This makes me wonder if it’s my Cloudflare firewall rules. If 390FawnDrive.com is forwarding to thomashenthorne.com and the Cloudflare firewall sees a repeat visit as a potential denial of service attack, couldn’t it theoretically reject the connection or issue a challenge?
As mentioned, Cloudflare is not involved here in the first place as that domain is not using any of its features here. So it’s not Cloudflare’s DNS, not Cloudflare’s firewall, not Cloudflare at all.
It would be only an issue if your Cloudflare domain did not load, but that’s not the case.
Remember that any connections to a FawnDrive domain have nothing to do with Cloudflare. Not until a browser executes the 301 redirect to connect to thomashenthorne does Cloudflare come into play.
OK thanks much to you both.