The initial backtrace and the can't resolve backtrace seem to be quite different.
The first looks like it would be triggered by some bad data coming over https where the other one is simply because resolving fails.
Catching the DNS resolution problem should be trivial, the initial traceback isn't exactly clear on what's going on though.
The initial backtrace and the can't resolve backtrace seem to be quite different.
The first looks like it would be triggered by some bad data coming over https where the other one is simply because resolving fails.
Catching the DNS resolution problem should be trivial, the initial traceback isn't exactly clear on what's going on though.