Short term user of Pi-Hole here, been an avid user of pfSense with SquidGuard for years but this project appeals to me. The Dashboard i.e. is great and so is the logging. To suit all DNS needs the project could be complemented with an DNS resolver, like Unbound . This way no external DNS servers nee…

Unbound can be run on the same device as the Pi-hole, you would just need to run Unbound on a different port and then change the upstream to point to that new port scheme. I run multiple Unbound installs on different VPSes and then forward my Pi-hole to those Unbound installs as upstreams. We have…

I can see it being usefull as being an option. Not to have both running because you have to.

And that's why it's in Feature Requests :grinning:

Got it. EDIT: at least it got bumped couple of times now :wink:

I knew I had seen this on the interwebs somewhere. I'm not sure if this link will help anybody or not. pi-hole-setup-methode-with-bind9 I haven't seen anything for unbound in my journeys. I'm also assuming that there would be a performance/speed cost to doing something like this.

Any update regarding this optional feature ?

With FTLDNS, we finally implement official support for this, read more details below. We, the Pi-hole core developing team, have discussed how to tackle this feature request best. It is clear that we do not want to implement this into our own DNS resolver at this stage, but want to rely on an alrea…

Works great thanks :grin: @DL6ER

Thanks, I like the workaround in the wiki article. However, a lot of potential of unbound is wasted. Especially the blocking option of unbound, which works much more effectively with an NXDOMAIN response than the timeout to 127.0.0.1. A very nice conversion offers GitHub - sfeakes/ipfire-scripts: …

Pi-hole Userspace

Add the ability to let Pi-Hole resolve DNS

Feature Requests Implemented

ftldns-beta

show post in topic

Home
Categories
Guidelines
Terms of Service
Privacy Policy

Powered by Discourse, best viewed with JavaScript enabled