Serve stale with reputation cache: version 1 (!534) · Merge requests · Knot projects / Knot Resolver · GitLab

GitLab now enforces expiry dates on tokens that originally had no set expiration date. Those tokens were given an expiration date of one year later. Please review your personal access tokens, project access tokens, and group access tokens to ensure you are aware of upcoming expirations. Administrators of GitLab can find more information on how to identify and mitigate interruption in our documentation.

Self sign-up has been disabled due to increased spam activity. If you want to get access, please send an email to a project owner (preferred) or at gitlab(at)nic(dot)cz. We apologize for the inconvenience.

Petr Špaček requested to merge serve-stale-rcache-v1 into master Mar 28, 2018

Reputation cache now caches that server is "dead" and resolver quickly falls back to stale data in cache.

This probably needs further optimization but we cannot move without experience from real networks.