On 5/8/2025 at 6:44 AM, ZappyZap said:

i do not use stubby anymore , of course i can re-add to let the option open for those who would like to use it

 

I will look at it

 

That would be really great. I just came to this support topic to ask the same thing after noticing stubby is no longer present.. seems like I'm not the only one. I was hoping to do an apples-to-apples comparison of Quad9 over DoH vs DoT, and would appreciate stubby being re-added to enable that. Thanks!

5 hours ago, 8vvhBHDAdb73grkPAYEU said:

 

That would be really great. I just came to this support topic to ask the same thing after noticing stubby is no longer present.. seems like I'm not the only one. I was hoping to do an apples-to-apples comparison of Quad9 over DoH vs DoT, and would appreciate stubby being re-added to enable that. Thanks!

i plan to propose something on this 
will let you know

All
please test the tag : v6-dev

 

DoH service (cloudflared) runs at 127.1.1.1#5153. Uses cloudflare (1.1.1.1 / 1.0.0.1) by default

DoT service (stubby) runs at 127.2.2.2#5253. Uses google (8.8.8.8 / 8.8.4.4) by default

Unbound service run at 127.0.0.1#5335

 

Use the "DNS upstream" fields to use what ever you want 
Upstream DNS server(s) for Pi-hole to forward queries to, separated by a semicolon.
127.1.1.1#5153;127.0.0.1#5335;127.2.2.2#5253

Note: The existence of this environment variable assumes this as the sole management of upstream DNS. Upstream DNS added via the web interface will be overwritten on container restart/recreation.

let me know how your test goes
 

On 5/11/2025 at 6:52 AM, ZappyZap said:

All
please test the tag : v6-dev

[..]

let me know how your test goes

Thank you for the quick fix. Stubby is working fine so far. 👍

Regarding gravity update interval: Were you able to find a solution by any chance? 🙃

Edited May 21, 20251 yr by paddesb

On 5/21/2025 at 6:42 AM, paddesb said:

Regarding gravity update interval: Were you able to find a solution by any chance? 🙃

Not yet

Did you push to the wrong tag? my v5 container got updated to v6 and broke.

EDIT: Looks like it

Edited June 10, 20251 yr by Kilrah

There is no more update on V5 , update your template with image: devzwf/pihole-dot-doh:2024.07.0

that's the latest V5

That's exactly why i delay so much the merge....i was afraid this happen to some users still on V5
i will update the v5 template

Thanks

Edited June 11, 20251 yr by ZappyZap

I mean I needed to move to v6 at some point... I've managed to fix it, it appears 04-pihole-static-dhcp.conf gets imported into a database or something on v6 instead of remaining a file, but on v5 i used to just edit the file manually and had commented out lines and entries for documentation/separation, the import is crap and just grabbed anything in there without respecting the commented out stuff so i ended up with invalid/duplicate entries that prevented it from starting.

Had to restore backup, modify the file to remove what it doesn't like and run the import again.

I had 2 custom dnsmasq conf files i don't know how to replicate the functionality of in v6, but i found the setting to make it load them so I'm good.

2 possible issues in the v6 template:

You must set FTLCONF_dns_upstreams variables to 127.1.1.1#5153 (DoH) and/or 127.2.2.2#5335 (DoT).

but the default doesn't match and the variable has an assigned value so it's just 127.1.1.1#5153 by default.

2nd is there's a TZ variable, but unraid automatically adds the one it's set to (so if the template adds one it's defined twice).

Edited June 11, 20251 yr by Kilrah

5 hours ago, Kilrah said:

I mean I needed to move to v6 at some point... I've managed to fix it, it appears 04-pihole-static-dhcp.conf gets imported into a database or something on v6 instead of remaining a file, but on v5 i used to just edit the file manually and had commented out lines and entries for documentation/separation, the import is crap and just grabbed anything in there without respecting the commented out stuff so i ended up with invalid/duplicate entries that prevented it from starting.

Had to restore backup, modify the file to remove what it doesn't like and run the import again.

I had 2 custom dnsmasq conf files i don't know how to replicate the functionality of in v6, but i found the setting to make it load them so I'm good.

Interesting, i did not had much testing with the migration on DHCP , only with fake data from my lab....
i do not use pihole as DHCP server...

5 hours ago, Kilrah said:

2 possible issues in the v6 template:

but the default doesn't match and the variable has an assigned value so it's just 127.1.1.1#5153 by default.

Good catch , overlook on my side , should be any combination of

• 127.1.1.1#5153 (cloudflared)

• 127.0.0.1#5335 (Unbound)

• 127.2.2.2@5253 (stubby)

i will fix that

5 hours ago, Kilrah said:

2nd is there's a TZ variable, but unraid automatically adds the one it's set to (so if the template adds one it's defined twice).

Correct , thanks for catching it , I will fix as well.

Edited June 11, 20251 yr by ZappyZap

11 hours ago, Kilrah said:

I mean I needed to move to v6 at some point... I've managed to fix it, it appears 04-pihole-static-dhcp.conf gets imported into a database or something on v6 instead of remaining a file, but on v5 i used to just edit the file manually and had commented out lines and entries for documentation/separation, the import is crap and just grabbed anything in there without respecting the commented out stuff so i ended up with invalid/duplicate entries that prevented it from starting.

Had to restore backup, modify the file to remove what it doesn't like and run the import again.

I had 2 custom dnsmasq conf files i don't know how to replicate the functionality of in v6, but i found the setting to make it load them so I'm good.

2 possible issues in the v6 template:

but the default doesn't match and the variable has an assigned value so it's just 127.1.1.1#5153 by default.

2nd is there's a TZ variable, but unraid automatically adds the one it's set to (so if the template adds one it's defined twice).

I do have one DNSMasq.conf file for my local domain (as I have internal DNS servers in my lab). How did you go about loading those configs into the new PiHole v6?

I think this is really my only custom mod so should upgrade to v6 fairly smoothly otherwise...

1 hour ago, Alyred said:

How did you go about loading those configs into the new PiHole v6?

Settings->All Settings->Misc, then

Gotta make sure your folder containing it is still mapped of course

Edited June 11, 20251 yr by Kilrah

On 6/11/2025 at 9:17 AM, ZappyZap said:

Interesting, i did not had much testing with the migration on DHCP , only with fake data from my lab....
i do not use pihole as DHCP server...

Good catch , overlook on my side , should be any combination of

• 127.1.1.1#5153 (cloudflared)

• 127.0.0.1#5335 (Unbound)

• 127.2.2.2@5253 (stubby)

i will fix that

Correct , thanks for catching it , I will fix as well.

I am seeing the following log entries after I was upgrade from 5 to 6 - I even went so far to blow away my appdata and start over. Not sure if this is an actual issue or not, but I thought I'd bring it to your attention.

2025-06-12 15:18:56.439 WARNING API: Not found (key: not_found, hint: /api/v1.0/public/device)

2025-06-12 15:19:08.638 WARNING API: Not found (key: not_found, hint: /api/v1.0/public/device)

I just setup Pihole-DoT-DoH and it works great but then, hey unbound seems cool. Is that available in the v6 version and is there a migration guide? Can I do a backup of my current version and import for the new one?

23 hours ago, Todilo said:

I just setup Pihole-DoT-DoH and it works great but then, hey unbound seems cool. Is that available in the v6 version and is there a migration guide? Can I do a backup of my current version and import for the new one?

unbouand is available in v6
about the migration, i did not test it so i cant answer this question.

On 6/12/2025 at 3:31 PM, updawg said:

I am seeing the following log entries after I was upgrade from 5 to 6 - I even went so far to blow away my appdata and start over. Not sure if this is an actual issue or not, but I thought I'd bring it to your attention.

2025-06-12 15:18:56.439 WARNING API: Not found (key: not_found, hint: /api/v1.0/public/device)

2025-06-12 15:19:08.638 WARNING API: Not found (key: not_found, hint: /api/v1.0/public/device)

I need to try to reproduce

16 hours ago, ZappyZap said:

unbouand is available in v6
about the migration, i did not test it so i cant answer this question.

Apparently it finds the configurationfile of old version and migrated without any manual setup. And unbound seems to be working great as well, so very happy running the new v6. Thank you

Finally had time to stage upgrades for my PiHole servers. Thanks @ZappyZap for your work, everything went great and was able to get v6 up and running with DNSMasq enabled, my old configs loaded fine.

And thanks @Kilrah for pointing me to the correct spot where to enable DNSMasq!

Any news on when the new update is avaiable?

4 hours ago, jankasten said:

Any news on when the new update is avaiable?

Totally my fault
I am so sorry, I disable the automation for some heavy lifting and forgot to re-enable it.....
Hope you will forgive me .... update has been push

11.11.2025 14:48:26 cloudflared version 2025.11.1 (built 2025-11-07-16:59 UTC) installed for x86_64

11.11.2025 14:48:27 Stubby 0.4.3 installed for x86_64

11.11.2025 14:48:28 Unbound Version 1.24.1 installed for x86_64

11.11.2025 14:48:29 Core version is v6.2.2 (Latest: v6.2.2) installed

11.11.2025 14:48:29 Web version is v6.3 (Latest: v6.3) installed

11.11.2025 14:48:29 FTL version is v6.3.3 (Latest: v6.3.3) installed

11.11.2025 14:48:29 Built from pihole/pihole with tag latest

Thx for your fast reply... No problem at all

Hey, sorry if this is a silly question - how can I update my v6 container like referenced in the post above? I converted from the old v5 a couple months ago and haven't kept up since - it's currently set on devzwf/pihole-dot-doh:latest-v6, but I haven't seen any updates in a long while and wanted to check if that had been deprecated.

9 hours ago, Outlaws said:

Hey, sorry if this is a silly question - how can I update my v6 container like referenced in the post above? I converted from the old v5 a couple months ago and haven't kept up since - it's currently set on devzwf/pihole-dot-doh:latest-v6, but I haven't seen any updates in a long while and wanted to check if that had been deprecated.

Hi
just use : devzwf/pihole-dot-doh:latest

Let me know how it is going.

Thanks

Perfect, I figured that was the next step and just wanted to confirm. Worked great!

Yikes. I just realized I've been running the deprecated Pihole-DoT-DoH tag=testdasi/pihole-dot-doh:latest, latest pi-hole v=5.18.3. I've been looking through these support pages and it kinda seems like maybe I can just install the devzwf docker from community applications directly on top of what I currently have installed, as long as I stop the testdasi docker first? Or am I missing something obvious? I feel like I'm missing something obvious. If I'm coming at this all wrong and someone's feeling generous, I would really appreciate anyone who is down to explain the migration process from testdasi to devzwf's current v6 tag.

thanks!!

2 hours ago, dexxy said:

Yikes. I just realized I've been running the deprecated Pihole-DoT-DoH tag=testdasi/pihole-dot-doh:latest, latest pi-hole v=5.18.3. I've been looking through these support pages and it kinda seems like maybe I can just install the devzwf docker from community applications directly on top of what I currently have installed, as long as I stop the testdasi docker first? Or am I missing something obvious? I feel like I'm missing something obvious. If I'm coming at this all wrong and someone's feeling generous, I would really appreciate anyone who is down to explain the migration process from testdasi to devzwf's current v6 tag.

thanks!!

Do you have a complex setup ?
if not start from scratch.....
if you do not want to go this route, backup you data folder and update the container... and go from there.