This is something we had reported last month, but I haven't had a chance to look into it. I believe the connection isn't properly cleaned up. I am building 8.4 final now, which will behave the same, but will be sure to get this addressed in future versions.
I hate to speculate on what is going on, but these things are certain:
- If it is the update check occurring even though update checks are disabled, then it's a bug - and probably passed our tests because it just doesn't tell you about the update
- If it is after a manual update, then the connection may not have been cleaned up properly.
- Other than product activation, there really aren't any other possibilities
- As you can see, no significant data is transferred, and the connection is just not cleaned up properly, so it's absolutely NOT any sort of 'call home' function
Topic moved to bug reports and I'll be tracking this closely. I may very well release a beta that resolves it in the coming day(s). Once I've tracked down the precise cause, I'll be able to tell you why it happened, etc...
Thanks for the report!
Apologies for the problem, and I'll post here when I have it resolved!And smart move running dnscrypt-proxy, I have tried to encourage as many people as possible to do the same. It's amazing that so few people consider the lack of DNS query encryption a serious issue.