Unbound, CoreDNS, and ThreatGate feature parity issue
-
PfSense Plus user here.
I’m all for modernizing the pfSense UI and getting away from the tech debt in the traditional UI. My concern is losing functionality along the way.
The CoreDNS implementation is still missing advanced features available with Unbound like configuring DoT. That leaves me wanting to stay with Unbound. But since ThreatGate requires CoreDNS, what happens when the traditional UI and pfBlockerNG are retired? How do users keep using Unbound and retain advanced DNS filtering?
Modernization makes sense, but removing existing features without a comparable alternative is a step backward. These are capabilities people already use and depend on.
Is the plan to bring CoreDNS to feature parity before retiring the existing options, allow ThreatGate to work with Unbound, or provide another supported path? What is the migration plan for users in this situation?
-
Is the plan to bring CoreDNS to feature parity before retiring the existing options
Yes.
It you're using it now you almost certainly have it running along side (forwarding to) Unbound. You still retain the features Unbound offers like DoT. But it would be better, IMO at least!, to run only one DNS service since they're both resource heavy. That can't happen until we have feature parity.
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register LoginPrivacy Policy · Cookie Policy