Parental Control DNS Filtering not working with PiHole

[dvaz]

Running Merlin's build 380.62_1

PiHole is a ad-filtering DNS server running on a raspi3.

I put the PiHole ip on the LAN section ( 192.168.1.250 )

And it seems to work fine, it routes all the DNS queries to that IP. The problem is that this breaks the previous DNS Filters for OpenDNS family that i had set up for my child devices.

If i got to the opendns www.internetbadguys.com on any of those devices ( or if i add another one to that list ) it shows that it no longer works.

It appers that the LAN DNS is overwritting the filterDNS. If i leave the LAN DNS black, opendns family filter works again.

Anyway around this?

Thanks!

 

[thelonelycoder]

- Ditch Pi-Hole as an ad-blocker and use your Raspberry for more interesting projects.
- Remove the PI IP in the Lan DNS Server section
- Install a popular Ad blocking solution on this forum on your router

If you leave your OpenDNS Settings as is, these devices will be directly served by the respective Service.
All other devices will have the benefit of ad blocking, happily done by the very same router

 

[martinr]

I use.a Raspberry Pi to block malicious domains. This is how my sertings look:

On the DNS Filtering page

Global Filter Mode is set to Router (rather than No filtering).

In the Client list at the bottom, only the Raspberry Pi is listed and that is set to No filtering. (No other clients are in that list.)

On the LAN DHCP Server page both DNS Servers are blank.

On the WAN > Internet Connection page I have both DNS Servers listed as the IP address of my Pi.

And now you must be wondering where does the OpenDNS server appear in all this?

In the Raspberry Pi, I have a file called dnsmasq.conf, which lists all the domains to be blocked,but above that list is the following header in which the OpenDNS addresses I use appear:

domain-needed
bogus-priv
no-resolv
domain=raspi.local
min-port=4096
no-dhcp-interface=
server=208.67.222.222
server=208.67.220.220
cache-size=10000

no-hosts
log-facility=/var/log/dnsmasq.log
log-async

address=/0000mps.webpreview.dsl.net/0.0.0.0
address=/0001.2waky.com/0.0.0.0
address=/001wen.com/0.0.0.0
..........

So if your Pi hole has a similar header in the equivalent file, you could try inserting/amending the server address to OpenDNS. Of course, if you do end up editing such a file the usual caveats apply when editing a linux/unix file with a Windows file editor. And of course make a backup of the file first just in case you break it when editing. (And note your current router settings in case you need to revert, or just backup the settings.)

And if all else fails, you could certainly follow thelonelycoder's advice eg his own solution (which he was too modest to put forwards) at http://www.snbforums.com/threads/release-ab-solution-3.35540/

 

[dvaz]

Oh, didn't know about ab-solution, thanks for pointing that out. Im going to look into it.

Thanks!

 

[dvaz]

- Ditch Pi-Hole as an ad-blocker and use your Raspberry for more interesting projects.
- Remove the PI IP in the Lan DNS Server section
- Install a popular Ad blocking solution on this forum on your router

If you leave your OpenDNS Settings as is, these devices will be directly served by the respective Service.
All other devices will have the benefit of ad blocking, happily done by the very same router

Thanks got it installed now. It does show a warning that DNS Filtering does not work during install, but everything seems fine. The two clients assigned in DNS Filtering still route thru OpenDNS sans adblocking as expected.

 

[thelonelycoder]

Thanks got it installed now. It does show a warning that DNS Filtering does not work during install, but everything seems fine. The two clients assigned in DNS Filtering still route thru OpenDNS sans adblocking as expected.

That's an intended warning that if you have set it to all devices, ad blocking will not work.
Yours works, just as pedictet.