spants

Have you set DNS1 and DNS2 variable to point to 8.8.8.8 or 1.1.1.1 ? If pihole doesnt need to block it, uses DNS1 and DNS2 to do the look up. Try posting a screenshot of your settings if not.

maybe its because of https://github.com/diginc/docker-pi-hole/issues/265? My template just calls diginc's docker so I have no control over it. Don't forget that you can change the repository to use a specific version by using tags https://hub.docker.com/r/diginc/pi-hole/tags/

The best way is to find the author of the node on flows.Nodered.org and raise an issue on github/slack/Google groups Tony

My node red template is for the official docker.... I used to work with the guys that wrote node red!... The mqtt one needed work to support passwords - these are imported and encrypted when the docker starts.

It is strange! I used to run it on the unraid ip with the unraid port changed. I then moved to separate ips and that works great for me. I do have two nics installed....

Why would you create another nodered docker and mosquito docker? What was missing from mine?

I just turn mine off just in case I want to use a normal dns ....

Nope - you have to wait until diginc tests and updates the docker

**** Spaceinvader One has created a setup video.. See it here ***

If you set dns1 and dns2 to Unbound, it gets changed?

Is your server at 192.168.1.22? (mine is!) Also a few post back it was found that unraid VM install pinches poet 53. I think if you disable VM, install, re-enable VM it should work (I think that was how people did it). I didnt have the problem....

did you try this:

strange, mine works well. Try clearing browser cache?

You have no queries or clients to graph.... are the clients pointing to your pihole server? When you go to Tools/Tail pihole.log, are things being added?

It shouldn't introduce latency, all it is doing is providing a dns lookup- the traffic should behave as normal

Look at the query log on the UI when visiting the site. It will tell you what is being blocked.

good to hear. I will create a script that people can run when the docker is updated. 1. Not sure why. As mentioned before I just made the simple template, digiinc did the hard work. It might be worth checking the github for it https://github.com/diginc/docker-pi-hole. (reminds me that I need to see if the bug for debian was fixed) 2. The script will need to be run again as it modifies the docker rather than being just data 3. I dont, sorry.

Your server ip is wrong, key 1 should be your pi-hole server ip. Currently the ads are being replaced by the unraid ui hence the password prompt

Hi guys, can you try the following to see if it speeds things up for you. I will roll it into a batch file so that you can run it after the docker is updated. 1. SSH to your Unraid server with pihole docker running 2. Copy and paste the following lines docker exec -it pihole apt-get update docker exec -it pihole apt-get --reinstall install iptables docker exec -it pihole apt-get install iptables-persistent docker exec -it pihole iptables -A INPUT -p tcp --destination-port 443 -j REJECT --reject-with tcp-reset docker exec -it pihole iptables -A INPUT -p udp --destination-port 80 -j REJECT --reject-with icmp-port-unreachable docker exec -it pihole iptables -A INPUT -p udp --destination-port 443 -j REJECT --reject-with icmp-port-unreachable docker exec -it pihole ip6tables -A INPUT -p tcp --destination-port 443 -j REJECT --reject-with tcp-reset docker exec -it pihole ip6tables -A INPUT -p udp --destination-port 80 -j REJECT --reject-with icmp6-port-unreachable docker exec -it pihole ip6tables -A INPUT -p udp --destination-port 443 -j REJECT --reject-with icmp6-port-unreachable docker exec -it pihole iptables-save > /etc/iptables/rules.v4 docker exec -it pihole ip6tables-save > /etc/iptables/rules.v6 Not sure if I need to change the "apt-get install" to "apt-get -y install" to accept the defaults - let me know...

I'm back from travelling... Will have a look over the next couple of days....

@CorneliousJD sorry I am away on business for a couple of weeks so will not be able to check. I run the log script with userscript plugin to keep the entries clear daily. @ebnerjoh a couple of the config directories are exposed but not sure you can get to hosts. You could change it in the docker but will have to reinstall mods on upgrade. Also change the exit DNS to opendns instead of 8.8.8.8

did you see a couple of posts up... There is a slight issue on the dockers that the author is addressing. The "extra parameters" tip solves it...

There is nothing I can do to "fix" this as the template is working as designed, I am not sure that Limetech will change the operation of unRaid. The solution is to use v6.4 and giving the pihole docker its own IP address.

Yep diginc docker update is broken :-( https://github.com/diginc/docker-pi-hole/issues/208 Change the repository to diginc/pi-hole:debian_v3.1.4 for a temporary fix until the request above is fixed.