Sara Dickinson

I think having the default on would be good, I thought an option might be useful so it could be disabled in case of interop problems (e.g a legacy XFR...

Did you manage to solve this problem? The only thing I can think of is that something else is now bound to that port at login time when the service...

OK - I think I am seeing the problem too and am a bit baffled at this stage. I'll have to try to dig into this but can't see an...

Hi there - this isn't possible with the current Stubby but a feature like this (and ideally re-trying timeouts) has been on our backlog a log time... Right now a...

I'm sorry I don't have any experience with ConnMan but a quick read up indicates it is a very low level integration with the OS that may be difficult to...

I'm closing this issue as no further updates in over 6 months but I'm going to mark is as a `known issue` because it wasn't resolved.

Also - depending on your environment/setup you may be able to enable full logging by passing the `-l` or `-v` flag to Stubby which will show you the connections Stubby...

Hi there - this issue here is with trying to use public key pinsets with Google who don't support them. You will see that the default `Stubby` config file does...

I think the issue here is the `idle_timeout` of 10000, which is long enough that the upstream is actually shutting the connection each time (instead of `stubby`) - see the...

Hi @cookiemonsteruk - a few initial comments/suggestions - You are on the right track with general logging for Stubby. Running it using `sudo /usr/local/bin/stubby -l -C /usr/local/etc/stubby/stubby.yml` should give you...