NOTIFY delayed 1s after DDNS or XFR. (1de98157) · Commits · Knot projects / Knot DNS · 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 1de98157 authored 8 years ago by

Libor Peltan

NOTIFY delayed 1s after DDNS or XFR.

This does not big harm on not-frequently updated zones, NOTIFY is simply delayed.
This helps on frequently updated (DDNS or [AI]XFR) zones - NOTIFY is not sent more often than once a second.

parent 345da3b8

Branches

Tags

1 merge request!638NOTIFY delayed 1s after DDNS or XFR.

Hide whitespace changes

Inline Side-by-side

Showing with 2 additions and 2 deletions

Please register or to comment