dns64-cname: correct order of CNAME and AAAA in answer (!324) · Merge requests · Knot projects / Knot Resolver

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.

Vitezslav Kriz requested to merge dns64-cname into master Jul 07, 2017

If CNAME chain occurs CNAME is placed before AAAA. #203 (closed) DNS64 synthesis not working for CNAME responses.

Admin message

Admin message

dns64-cname: correct order of CNAME and AAAA in answer

Merge request reports