ranbel

We have a section on connecting locations: https://developers.cloudflare.com/cloudflare-one/policies/filtering/initial-setup/dns/#connect-dns-locations What other on-ramps were you thinking of?

Closing this issue because we already link to DoH instructions.

Hey @simeyla, Cloudflare is deprioritizing locally-managed tunnels (i.e. YML file configuration) and recommending that customers use [remotely-managed tunnels](https://developers.cloudflare.com/cloudflare-one/connections/connect-networks/get-started/create-remote-tunnel/). For a remotely-managed tunnel, noTLSVerify and [loglevel ](https://developers.cloudflare.com/cloudflare-one/connections/connect-networks/monitor-tunnels/logs/#dashboard)are configured in the dashboard....

Hi @boutzamat, thanks for opening this issue! We are adding the missing mobile client instructions to #13080.

@dh-cf for guidance on > how to restore this file to the default, and what to do if the error persists when the file has the default contents.

Resolved in #14702

Hi @Explosion-Scratch, thanks for opening this issue. Could you provide the command output that shows which app is on port 53?

From a documentation perspective, the command output should match what a user sees when they are experiencing the error. So it should show an example of third-party processes bound to...

@dh-cf

Updated docs with more information on mDNSResponder: #13983