Ceyarrecks Wunnfirr's community posts

through CloudFlare(CF) automation, the request Titled: [Cloudflare Support] 1976738 - anti-Porn/Malware CF DNS BLOCKING RU; Default CF DNS allows is being stated as closing. At least this post will establish their ticket number that RU may refer to it.

Excuse me Please:

I am finding the process to address this subtle CloudFlare DNS problem is quickly getting beyond me.
Here is the latest response received:

=======
Sep 18, 2020, 3:29 AM PDT

Hi,
Issues with public resolver, including 1.1.1.1 for Families, are triaged and processed by a different team when submitted via the aforementioned form. They will take care of your request and the request of the company that is affected by this issue as long as you and the company submit this information through the supported channel.

Thanks for your understanding.

Sincerely,
Nikita | Technical Support Engineer
Search the Cloudflare Community for advice and insight.
=======

I do not understand how to proceed; as I frequently receive emails from CloudFlare that state "Your ticket has been deleted." And then to receive yet another email like the one above.
/shrug.

I want to Thank You for the alacrity of your response.
In the process of submitting a ticket with CloudFlare, their mid-step "diagnostics" stated the following:

The authoritative nameservers for remoteutilities.com are set incorrectly. For Cloudflare to activate, your domain registrar must point to the two nameservers provided by Cloudflare as the authoritative servers. Set your authoritative nameservers in your registrar’s admin panel (contact your registrar for support). Review changing your nameservers.

   The origin web server for remoteutilities.com is responding slowly to initial requests for uncached HTML content. To remove this performance bottleneck, look at your server’s ability to return HTML faster and/or implement HTML caching in Cloudflare. You may benefit from caching static HTML and anonymous page views. Learn how to do this in: WordPress, Drupal and Magento.

Which needless to say is well beyond my experience. Does the above mean anything?
Ticket with Cloud Flare submitted, ticket # available upon request.

after tinkering, I find that the Cloud Flare anti-porn/malware DNS (1.1.1.3 / 1.0.0.3) is blocking "id.remoteutilities.com."
switching to default Cloud Flare DNS (1.1.1.1 / 1.0.0.1) does NOT have such limitation.

would setting up one's own RU Server allow one to retain the above protections while allowing unrestricted Remote Utilities?
would there be any caveats?

Thank you for the time spent in thoughtfully replying.