rrcache: don't clobber pkt if failing the second step (!274) · Merge requests · Knot projects / Knot Resolver · GitLab

Snippets Groups Projects

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 Vladimír Čunát requested to merge rrcache-pkt-clobber into master 7 years ago

All threads resolved!

I hope fixing this bug should diminish the recent experiences of Google domains failing to resolve on Turris Omnia.

Activity

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

Author Owner

The problem manifested by sending a bad packet to the authoritative (containing the answer), getting FORMERR back and logging as ignoring mismatching response.
Vladimír Čunát mentioned in issue #179 (closed) 7 years ago

mentioned in issue #179 (closed)
Vladimír Čunát mentioned in issue #178 (closed) 7 years ago

mentioned in issue #178 (closed)
Vladimír Čunát @vcunat · 7 years ago

Author Owner

BTW, the patch can be safely applied to 1.2.5.
Petr Špaček @pspacek started a thread on an old version of the diff 7 years ago

Resolved 7 years ago by Petr Špaček
Last reply by Petr Špaček 7 years ago

Vladimír Čunát added 1 commit 7 years ago

added 1 commit

488b38c0 - rrcache: don't clobber pkt if failing the second step

Compare with previous version

Vladimír Čunát added 1 commit 7 years ago

added 1 commit

449af37b - rrcache: don't clobber pkt if failing the second step

Compare with previous version

Vladimír Čunát added 1 commit 7 years ago

added 1 commit

a42a8af9 - rrcache: don't clobber pkt if failing the second step

Compare with previous version

Petr Špaček resolved all discussions 7 years ago

resolved all discussions

Petr Špaček merged 7 years ago

merged

Petr Špaček mentioned in commit 7 years ago

mentioned in commit 7517d5da

Please register or sign in to reply