selection: force resolution of new NS name after lame delegation (34b735bd) · Commits · Knot projects / Knot Resolver · GitLab

Snippets Groups Projects

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.

Commit 34b735bd authored 4 years ago by

Štěpán Balážik

selection: force resolution of new NS name after lame delegation

Lame delegations are weird, they breed more lame delegations on broken
zones since trying another server from the same set usualy doesn't help.
We force resolution of another NS name in hope of getting somewhere.

parent 8d420324

Branches

Tags

1 merge request!1126Rework iterate.c/selection.c error handling

Hide whitespace changes

Inline Side-by-side

Showing with 19 additions and 1 deletion

Please register or to comment