You are not using secure transport for your DNS

The issue I am facing:

You are not using secure transport for your DNS

Details about my system:
Raspberry pi 4

What I have changed since installing Pi-hole:
DNS, enabled dhcp on pi hole etc so I can get device names and stuff, ad lists.







Secured DNS in this case means either DNS-over-TLS (DoT) or DNS-over-HTTPS (DoH). You need additional software to take advantage of either technology.

https://docs.pi-hole.net/guides/dns/cloudflared/

2 Likes

I’ll do this after I ask my friend if he has this installed as it says his dns is encrypted and he has the exact same settings as me apart from DHCP enabled on pi hole.

Nvm it’s because he’s using CF warp

Ok it's all setup I used this tutorial https://nathancatania.com/posts/pihole-dns-doh/

Using Cloudflare and I turned DNS sec off and ESNI checker is still saying it's insecure even though it's working I checked the status changed the upstream dns to 127.0.0.1#5053 and everything.

I also tried the esni checker on pi browser and still the same results

I checked the cloudflared status on the pi too and its working

pi@yup:~ $ sudo systemctl status cloudflared
● cloudflared.service - cloudflared DNS over HTTPS proxy
Loaded: loaded (/lib/systemd/system/cloudflared.service; enabled; vendor preset: enabled)
Active: active (running) since Sat 2021-05-22 10:34:54 BST; 9min ago
Main PID: 1440 (cloudflared)
Tasks: 10 (limit: 4915)
CGroup: /system.slice/cloudflared.service
└─1440 /usr/local/bin/cloudflared proxy-dns --port 5053 --upstream https://1.1.1.1/dns-query --upstream https://1.0.0.1/dns-query

May 22 10:34:54 yup systemd[1]: Started cloudflared DNS over HTTPS proxy.
May 22 10:34:54 yup cloudflared[1440]: 2021-05-22T09:34:54Z INF Adding DNS upstream url=https://1.1.1.1/dns-query
May 22 10:34:54 yup cloudflared[1440]: 2021-05-22T09:34:54Z INF Adding DNS upstream url=https://1.0.0.1/dns-query
May 22 10:34:54 yup cloudflared[1440]: 2021-05-22T09:34:54Z INF Starting DNS over HTTPS proxy server address=dns://localhost:5053
May 22 10:34:54 yup cloudflared[1440]: 2021-05-22T09:34:54Z INF Starting metrics server on 127.0.0.1:45367/metrics
May 22 10:41:18 yup cloudflared[1440]: 2021-05-22T09:41:18Z ERR failed to connect to an HTTPS backend "https://1.1.1.1/dns-query" error="failed to perform an HTTPS request: Post "https://1.1.1.1/dns-query": net/http: request canceled (C
May 22 10:41:18 yup cloudflared[1440]: 2021-05-22T09:41:18Z ERR failed to connect to an HTTPS backend "https://1.1.1.1/dns-query" error="failed to perform an HTTPS request: Post "https://1.1.1.1/dns-query": context deadline exceeded (Cl
May 22 10:41:23 yup cloudflared[1440]: 2021-05-22T09:41:23Z ERR failed to connect to an HTTPS backend "https://1.0.0.1/dns-query" error="failed to perform an HTTPS request: Post "https://1.0.0.1/dns-query": net/http: request canceled (C
May 22 10:41:23 yup cloudflared[1440]: 2021-05-22T09:41:23Z ERR failed to connect to an HTTPS backend "https://1.0.0.1/dns-query" error="failed to perform an HTTPS request: Post "https://1.0.0.1/dns-query": net/http: request canceled (C

pi@yup:~ $

Now i'm getting failed to connect hmm

After running sudo systemctl restart cloudflared those errors are gone

This seems unstable should I move to DNS crypt?

This can be closed it all works

This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.