July 5, 20233 yr Author why do you think it is something with the images? there is many people using it and do not have this issue. Let try debug it.... what did you try to conclude it is the image who is the culprit ?
November 23, 20232 yr Hi @ZappyZap thanks for updating the container! Do you post changelogs for it anywhere? I couldn't find one but I might just not be looking in the same place. Seems to be working fine but was just curious on the latest changes that have had a few updates this week. Thanks again!
November 23, 20232 yr Author 4 hours ago, Alyred said: Hi @ZappyZap thanks for updating the container! Do you post changelogs for it anywhere? I couldn't find one but I might just not be looking in the same place. Seems to be working fine but was just curious on the latest changes that have had a few updates this week. Thanks again! Yup https://github.com/devzwf/pihole-dot-doh
February 1, 20242 yr Hi, thanks for providing this! I'm pretty new to Unraid and Pi hole. But I finally managed to get it all up and running, and Pi hole is blocking away. 👍 One thing though. My dashboard reports a number of active clients. Clicking on the link, the Network overview page is empty, I only see the message "No data available in table" I did a lot of googling but can't seem to find an applicable cause or a solution. Any ideas what might cause this for me? What additional info would you potentially need from me? Again, pretty noob here.... Thanks!
February 7, 20242 yr On 2/1/2024 at 5:23 PM, ZappyZap said: I will have to dig a bit on this one as i coulr not reproduce Just wanted to let you know that I went with the official pihole docker now and have my Fritzbox do the dot lookups. Works very well and here all clients are showing fine. So, as far as I'm concerned, no need to look into this any further.
March 25, 20242 yr Author Container updated .... 21.03.2024 01:16:19 cloudflared version 2024.3.0 (built 2024-03-20-1010 UTC) installed for amd64 21.03.2024 01:16:19 Unbound Version 1.19.3 installed for amd64 21.03.2024 01:16:20 Built from pihole/pihole with tag latest and while we are at it , container also unbound ready for your use it listening on "127.0.0.1#5335" thanks
March 25, 20242 yr Author Any time. For stubby, i am installing the version from debian repo. and seems it has not been updated there...... I could of course compiled from source , i will will see. thanks
March 26, 20242 yr Author Quote Testing unbound now. Decided to leave docker template alone and just add another server by adding a config to dnsmasq folder: (Not sure if i can add that ip to the template.) I have to edit the template. will be done soon, just working on something else at the moment remove DNS1 and DNS2 Variable and add : PIHOLE_DNS_ with value : 127.0.0.1#5335 Edited March 26, 20242 yr by ZappyZap clarification
March 27, 20242 yr @ZappyZap will you update your docker to include unbound like @bmartino1 has implemented?
March 27, 20242 yr Author Hi, It is my plan to do it this week to be clear , the image is already updated. i need to update the template, i hope that's what you mean ? Edited March 27, 20242 yr by ZappyZap
March 27, 20242 yr @ZappyZap I will be honest, I just installed PiHole on unRAID. I have for years been using a raspberry Pi with PiHole and Unbound, but my Pi died. So I decided to move it to unRAID. I have a Ubiquiti network setup so I am routing all DNS (port 53) traffic to Pi Hole. I also block all requests from NOT using the PiHole. I saw your template had DOT and DOH, which I have not used before. But I noticed it did not have Unbound and I just found this forum thread. Question about DOT and DOH, since my network routes all DNS traffic to Pi Hole, does PiHole convert it to DOH/DOT? Or do I need to do similar Ubiquiti configs to route all that traffic to PiHole too? I have been trying to do reading on how it works but I don't understand it.
March 27, 20242 yr Author @ArstenA short answer Yes Long answer , is yes and now it also include unbound. so to use DOT/DOH : you set the variable PIHOLE_DNS_ to 127.2.2.2#5253;127.1.1.1#5153 Unbound : you set the variable PIHOLE_DNS_ to 127.0.0 127.0.0.1#5335 Of course, you can also configure the in the DNS tab of the pihole settings.
March 27, 20242 yr 7 hours ago, ArstenA said: Ok, so is it not possible to use DOT/DOH with Unbound? it depends on the dns queries that comes in. In my setup, I have dot/doh via docker template handling the queries, but unbound will overtake as a recursive dns. It will still use my dot/doh settings but all dns queries now run through unbound.
March 27, 20242 yr 10 hours ago, ArstenA said: @ZappyZap I will be honest, I just installed PiHole on unRAID. I have for years been using a raspberry Pi with PiHole and Unbound, but my Pi died. So I decided to move it to unRAID. I have a Ubiquiti network setup so I am routing all DNS (port 53) traffic to Pi Hole. I also block all requests from NOT using the PiHole. I saw your template had DOT and DOH, which I have not used before. But I noticed it did not have Unbound and I just found this forum thread. Question about DOT and DOH, since my network routes all DNS traffic to Pi Hole, does PiHole convert it to DOH/DOT? Or do I need to do similar Ubiquiti configs to route all that traffic to PiHole too? I have been trying to do reading on how it works but I don't understand it. To implement my setup, add 99-upstreamdns.conf and 99-edns.conf to the (dnsmasq.d folder) under appdata in unraid path via your template. The other configs exist in the /config path location 99 Upstreams contains other pihole dns server that it can use for DNS queries. The docker template should use dot/doh, and you can see that it is implementing the dot/doh under pihole > setting > dns. If you place a checkbox to other dns severe to use here, it would write to a config that is replaced on docker reboot the option I want to use can be added to another config which is the 99-upstreamdns.conf the severer option in this config is the same as selecting the other checkbox and not to use custom. the template regenerates this based on an option set in the template. Unfortunate, its up to pihole / dns query that comes in to then determine the dns system that it uses. This mean that Upstreams dns config may become the primary DNS server. as you can see in my piehole site which server is used more, in my case unbound is used more. And the server to doh/dot are listed and available when needed. Per the template data, unbound config is using pihole_dns and is using (stuby/cloudfare) dot/doh server setting for queries when needed. To help ease this, I add a dns record for piohole_dns to 127.0.0.1(Localhost) to help point it to local host for these queries. Edited March 27, 20242 yr by bmartino1
March 27, 20242 yr It not known or really talked about... so here is Some side networking information: Then to use pihole as some device I can't manually set. I use the ICS DCHP (https://www.isc.org/blogs/isc-dhcp-eol/) server to set dhcp option 6 while it is EOL it is still the defeat known reliable. But atm may be subject to CVE security issues. DHCP Option 6 set the dns servers your network and devices can talk to. Each router is different. using custom router firmware ddwrt/openwrt, or a PC router pfsense/opensense/ipfire/openwrt/etc... My network is using a firewalla purple device. So I add this option for firewalla(a ubuntu router) Firewalla ap: Network > Lan > edit > add dchp option: option code 6 option value: ipdns,ipdns,ipdns ddwrt: web UI > service tab > other dnsmasq options... dhcp-option=6, x.x.x.x, y.y.y.y openwrt was a dhcp config edit Ipfire no longer supports dhcp option 6 due to ICS DHCP discontinued and new ICS KEA implementation: https://www.isc.org/dhcp_migration/ pfSense is in the middle of changing over to it. atm ICS KEA doesn't have full support for dhcp options. I like dhcp option 6 as my dhcp server giving out ip can give all the dns server i want a client on my network access to to use as a domain/search domain. Usually piehole IP first, then router, then third party such as opendns, google, cloudfare... With doh implementation and some device and apps uses a coded dns server... such as kindles, e-readers, etc that don't have a interface to manually set ip address settings it good to have this DHCP option 6 set to assign them via the server and not at each client. PSA: It is unknown at this time if wifi routers manufactures(netgear, tplink, linksys, belkin, wavelink...etc) are still use isc dhcp over ics kea. Nor an announcement of newer devices and which dhcp server they use... Regardless, look into your routers manufacture and information as it may need to be replaced. I mention this as pihole does have a dhcp server that is forked from dnsmas built upon ICS DHCP Edited March 27, 20242 yr by bmartino1
May 9, 20242 yr 32 minutes ago, bmartino1 said: sad panda... i don't know what you changed or did. fresh docker install: i ahve atempted to tuncate -s 0 /var/log/pihole.FTL.log do a 1 to 1 to remove that log out https://discourse.pi-hole.net/t/disk-getting-full-cant-free-space/52800/2 run pihole flush sqlite3 /etc/pihole/pihole-FTL.db "VACUUM;" So I delete the template, docker image and files and Also did a fresh installation with the same... also says DB is full New file paths ... so something broke in the update! turned out to be unraid btrfs log file form all the dockers it didn't reset per other scripts and configs... had to delete my docker vdisk. I decide to increase the size and leave btrfx, used docker xfs. No issues now.
June 23, 20242 yr sad panda. new pihole problem. The docker doesn't seem to be getting the correct resolv.conf. at starting Cloudflare In log I get Starting unbound Starting stubby Starting cloudflared 2024-06-23T21:43:07Z WRN Your version 2024.6.0 is outdated. We recommend upgrading it to 2024.6.1 [✗] DNS resolution is currently unavailable when I console to the docker at root@PIHOLEDOHDOT:/# cat /etc/resolv.conf file, I get: root@PIHOLEDOHDOT:/# cat /etc/resolv.conf nameserver 127.0.0.11 options ndots:0 root@PIHOLEDOHDOT:/# ^for stuby/Cloudflare this should be 127.0.0.1 and or other upstream dns servers. Pihole works normally otherwise. But dockers autostart and pihole -up / pihole -g never starts the gravity update.... when it should be pulling unraids resolve.conf: root@BMM-Unraid:~# cat /etc/resolv.conf # Generated by rc.inet1 nameserver 192.168.2.1 nameserver 208.67.222.222 nameserver 9.9.9.9 Edited June 23, 20242 yr by bmartino1
June 23, 20242 yr 18 hours ago, bmartino1 said: sad panda. new pihole problem. THe docker donw't seem to be getting the correct resolv.conf. at starting Cloudflare i get Starting unbound Starting stubby Starting cloudflared 2024-06-23T21:43:07Z WRN Your version 2024.6.0 is outdated. We recommend upgrading it to 2024.6.1 [✗] DNS resolution is currently unavailable when I console to the docker at root@PIHOLEDOHDOT:/# cat /etc/resolv.conf file, I get: root@PIHOLEDOHDOT:/# cat /etc/resolv.conf nameserver 127.0.0.11 options ndots:0 root@PIHOLEDOHDOT:/# ^for stuby/Cloudflare this should be 127.0.0.1 and or other upstream dns servers. Pihole works normaly other wise. but dockers autostart and pihole -up / pihle -g never starts the gravity update.... when it should be pulling unraids resolve.conf: root@BMM-Unraid:~# cat /etc/resolv.conf # Generated by rc.inet1 nameserver 192.168.2.1 nameserver 208.67.222.222 nameserver 9.9.9.9 I was able to fix this by creating a 1 to 1 file for the docker My resolve conf contains: root@PIHOLEDOHDOT:/# cat /etc/resolv.conf #Docker Default: nameserver 127.0.0.11 options ndots:0 #Local Machine nameserver 192.168.2.10 nameserver 127.0.0.1 #Unriad: # Generated by rc.inet1 nameserver 192.168.2.1 nameserver 208.67.222.222 nameserver 9.9.9.9 #My other Upstream DNS: #domain localdomain #search localdomain nameserver 130.126.2.131 #nameserver 8.8.8.8 #nameserver 1.1.1.1 #Docker local DNS: #stubby(DOT) and cloudflare(DOH) nameserver 127.1.1.1#5153 nameserver 127.2.2.2#5253 #unbound: nameserver 127.0.0.1#5335 root@PIHOLEDOHDOT:/# Edited June 24, 20242 yr by bmartino1 Corect update dns in resolve conf
June 23, 20242 yr this appears to be happening as my local LAN is now 192.168.2.1 and not the default home router domains of 192.168.1.1 found in the dnsmasq conf that is forcibly overwritten at docker start: as i edited that conf earlier and set them both to 192.168.2.X to fix this... with out being able to edit the file 01-pihole.conf under the dnsmasq folder. https://docs.pi-hole.net/ftldns/configfile/ I'm presented with a failed resolv.conf with no dns resolver. To fix this i have to make another 99-fix-pihole-01.conf https://docs.pi-hole.net/ftldns/configfile/ ^I also edit my etc ftl conf and this requires me to have the config edit to add option domain. with the correct information The docker would need a code update for first run to download and a check if to not download... Edited June 23, 20242 yr by bmartino1
.thumb.jpg.bec61e4e919a9235cc4475f8cb53d5e3.jpg)
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.