Ranter
Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
Comments
-
@Wack I am not sure about DNS cache on pi.hole, so I wanted to give this a try. I like to test things when I am trying to learn more about something. :)
-
I figured out a way to fix that. I am not sure why, but Unbound were not accepting the Stubby port configuration. So I changed Stubby ip to a different one, keeping the default port and everything is working fine.
-
Well, forget about it. On my last test I forgot to delete the Unbound entry to Quad-9.
It is still not working. -
Forgot to say, but I found the problem. I didn't had the Unbound keys. I set them and everything is working.
But now I am going to ditch Stubby as Unbound has DNS over TLS and DNSSEC.
Related Rants
I have configured on my local desktop a pi.hole and Stubby. They were working fine and happy together, but after a comment from @FrodoSwaggins about local DNS server, I trying to add Unbound as well.
So, on my configuration, pi.hole points to unbound, which points to Stubby. Everything local, each one with their own ip@port listener, but it does not work.
If I point Unbount to an external DNS (Quad9, for exemple), it works. If I point pi.hole to Stubby, it works. But the 3 of them does not work.
Does anyone has any idea what could be happening?
Thanks!
question
unbound
pi.hole
stubby
dns
dns server