*Temp Solution in Reply* DNS-Over-HTTPS not working after updating to V6

[Aviator85]

Expected Behaviour:

I've had an RPI setup using the cloudflared DNS-Over-HTTPS for years. Originally with a RPI 4, now with a newer RPI5 like a year or 2 ago

Last night I stupidly updated pi-hole and it failed so reimaged it with new raspian lite and did a clean install then followed the same instructions for cloudflared DNS-Over-HTTPS at cloudflared (DoH) - Pi-hole documentation

Actual Behaviour:

After changing to custom server 127.0.0.1#5053 it does not work. If I delete the custom server and check the 2 defualt boxes for Cloudflare DNSSEC its back up and running

I'd really like to get my DNS-Over-HTTPS back up and running - any help would be greatly appreciated

Debug Token:

Working debug when using the defualt upstream 2 IPv4 check boxes for Cloudflare (DNSSEC) https://tricorder.pi-hole.net/cpIyrqAn/

Non-working debug After unchecking the 2 boxes for IPv4 for the Cloudflare (DNSSEC) and entering the custom server 127.0.0.1#5053 https://tricorder.pi-hole.net/1qvp8gd2/

[Aviator85]

I just found its a known issue and theres a quick easy fix for this.

go to Settings>All Settings>Miscellaneous>misc.dnsmasq_lines and add this text in between the quotes "no-0x20-encode" and save

And be sure the custom server says 127.0.0.1#5053 like it says in DoH instructions

Source:

V6 - Post release fixes and findings

Originally published at: V6 – Post release fixes and findings – Pi-hole Well, what a busy couple of days! We have finally released v6 – and we believe by-and-large that it has been a success! Of course, there will be a few bugs and issues that weren’t caught during testing, even with the extended beta release we were probably never going to catch everything – so we’re always keen to fix new issues as soon as they come up after a release. We’ve already released a couple of hotfixes, details…

You can verify its working by going to 1.1.1.1 — One of the Internet’s Fastest, Privacy-First DNS Resolver it will tell you if DoH is working

Hopefully a real fix comes out for it

[Aviator85]

I'm having the same exact issue!

tried updating to V6 and it failed - did a fresh raspian lite image installed exactly how i had it before but when installing the cloudflared DOH DNS-over-HTTPS, removing the custom server and selecting the default Cloudflare (DNSSEC) got it working but I would like to have my cloudflared (DoH) back up and running

Here's my help post

*Temp Solution in Reply* DNS-Over-HTTPS not working after updating to V6

Expected Behaviour: I've had an RPI setup using the cloudflared DNS-Over-HTTPS for years. Originally with a RPI 4, now with a newer RPI5 like a year or 2 ago Last night I stupidly updated pi-hole and it failed so reimaged it with new raspian lite and did a clean install then followed the same instructions for cloudflared DNS-Over-HTTPS at cloudflared (DoH) - Pi-hole documentation Actual Behaviour: After changing to custom server 127.0.0.1#5053 it does not work. If I delete the custom server an…

[rdwebdesign]

@pihole4

For some reason, I don't see an option to generate a debug log via the web interface

You won't see it anymore.

For security reasons the user used to run the web interface was changed and it doesn't have enough permissions to execute the debug log.

You will need to execute pihole -d on a terminal.

[Aviator85]

I just found its a known issue and theres a quick easy fix for this.

go to Settings>All Settings>Miscellaneous>misc.dnsmasq_lines and add this text in between the quotes "no-0x20-encode" and save

And be sure the custom server says 127.0.0.1#5053 like it says in DoH instructions

Source:

V6 - Post release fixes and findings

Originally published at: V6 – Post release fixes and findings – Pi-hole Well, what a busy couple of days! We have finally released v6 – and we believe by-and-large that it has been a success! Of course, there will be a few bugs and issues that weren’t caught during testing, even with the extended beta release we were probably never going to catch everything – so we’re always keen to fix new issues as soon as they come up after a release. We’ve already released a couple of hotfixes, details…

You can verify its working by going to 1.1.1.1 — One of the Internet’s Fastest, Privacy-First DNS Resolver it will tell you if DoH is working