dns64-cname: correct order of CNAME and AAAA in answer (!324) · Merge requests · 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.

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

dns64-cname into master

Merged Vitezslav Kriz requested to merge dns64-cname into master 7 years ago

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

Activity

Vladimír Čunát assigned to @vcunat 7 years ago

assigned to @vcunat
Vladimír Čunát added 2 commits 7 years ago
added 2 commits

41b2544a - lua nitpicks: memory management

0d930172 - NEWS, docs: update dns64 info

Compare with previous version
Vladimír Čunát @vcunat · 7 years ago

Owner

I have to fixup some problems with policy.FORWARD.
Vladimír Čunát added 2 commits 7 years ago
added 2 commits

0b748e0e - dns64: improve with policy.FORWARD or .STUB

df52a663 - NEWS, docs: update dns64 info

Compare with previous version
Vladimír Čunát changed milestone to %1.3.2 7 years ago

changed milestone to %1.3.2
Vladimír Čunát merged 7 years ago

merged
Vladimír Čunát mentioned in commit bc3d2159 7 years ago

mentioned in commit bc3d2159

Please register or sign in to reply