Changed implementation of rrset_next_dname. (89a95922) · Commits · Daniel Kahn Gillmor / 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 89a95922 authored 12 years ago by

Jan Kadlec

Changed implementation of rrset_next_dname.

- No need for block number now
- Added similar function, but works only on one RR.

parent 699ccc5b

Branches

Tags

No related merge requests found

Hide whitespace changes

Inline Side-by-side

Showing with 135 additions and 107 deletions

Please register or to comment