Sara Dickinson

Hi - it is the first behaviour you describe - it is an instruction to the recursive resolver not to use ESC when resolving the query (so the client subnet...

Hi there, Can you point to where you found this as I think it needs some correction/clarification. Some of the criteria only make sense for Unbound when acting as a...

So I'm a bit confused by this one. In getdns-1.6.0/stubby-0.3.0 (Openwrt 19.07) a fix was included to prevent the issue where stubby was sending back responses that were larger than...

Did you solve this problem. `Stubby` will only forward to whatever resolvers are configured in the stubby configuration file. Are you able to share your config file? Also please double...

A quick answer is that this sounds like a permissions issue.... what are the permissions on the `dnssec_trust_anchors` file e.g. if it was created while stubby was running as root...

@wtoorop @ArchangeGabriel My proposal is a quick fix that reverts to `PrivateUsers=False`. Not ideal but it is the least disruption as it reverts to the 0.4.0 situation (I do know...

Closing this as addressed by 0.4.3 release

This is indeed a limitation of the Stubby Manager GUI, not `stubby` itself, so recommendation is to install via the msi/zip installer and manage a service for a IPv6 only...

Have a look at https://github.com/getdnsapi/stubby/pull/324 Does changing that user to false fix the problem?

Thanks for reporting this. I'm going to close it as a known issue as the 0.4.3 update to set `PrivateUsers=false` seems to work on all other platforms.