"Too many incoming connections (max=2000" when internet is down and then is restored

[MNLierman]

I can't comment in the last issue from 2021 but this is most definitely still not fixed, not even in the slightly. A better implementation would be to create a variable in the .conf file that says something like drop connections when there is no connectivity. Like don't keep filling it. Right now my internet is now restored but DNSCrypt will not work again until ssh into it and do systemctl restart dnscrypt-proxy. Until then, my internet perpetually is down because DNS is down because DNSCrypt remembers all of the failed DNS requests and just holds onto them. There should be a TTL for failed requests, I think that's what I'm going for here. A TTL for that request, a DNS request from a client to a server is only good for so long because the client will keep requesting over and over again trying to check when internet is back up. At some point it needs to drop all of the DNS requests that it can't possibly fulfil, and why would a client want them minutes later? I was hoping to find a timeout or TTL variable that I could uncomment in the .conf to enable it to drop all requests that are just sitting there. I even upped my connection limit and it doesn't matter how high you make it.

[github-actions]

This issue was automatically closed because it did not follow the issue template. We use the issue tracker exclusively for bug reports and feature additions that have been previously discussed. However, this issue appears to be a support request. Please use the discussion forums for support requests.