Commit 3aca907
authored
Fix bug with SOA records not updating correctly (#266)
Note that the SOA record is stored twice: once in the zones table (the
`authority` section of the `#zone{}` record), and another one as a
standalone RRSet in the typed records table. And then the resolution
algorithm would use the RRSet in the typed records table as the answer
for an explicit query to SOA records but the cached ones on the zone
record for any other query that required including SOA records. This
would be an issue for DNSSEC, because for example an NSEC answer would
include the RRSIG record of the _new_ SOA record, but with the _old_ SOA
record, hence triggering a validation failure.
Note that this code was available in v7, and it was lost just very unfortunately. The PR comes with a regression test.1 parent 227f81c commit 3aca907
2 files changed
+43
-1
lines changed| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
505 | 505 | | |
506 | 506 | | |
507 | 507 | | |
508 | | - | |
| 508 | + | |
| 509 | + | |
| 510 | + | |
| 511 | + | |
| 512 | + | |
509 | 513 | | |
510 | 514 | | |
511 | 515 | | |
| |||
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
66 | 66 | | |
67 | 67 | | |
68 | 68 | | |
| 69 | + | |
69 | 70 | | |
70 | 71 | | |
71 | 72 | | |
| |||
738 | 739 | | |
739 | 740 | | |
740 | 741 | | |
| 742 | + | |
| 743 | + | |
| 744 | + | |
| 745 | + | |
| 746 | + | |
| 747 | + | |
| 748 | + | |
| 749 | + | |
| 750 | + | |
| 751 | + | |
| 752 | + | |
| 753 | + | |
| 754 | + | |
| 755 | + | |
| 756 | + | |
| 757 | + | |
| 758 | + | |
| 759 | + | |
| 760 | + | |
| 761 | + | |
| 762 | + | |
| 763 | + | |
| 764 | + | |
| 765 | + | |
| 766 | + | |
| 767 | + | |
| 768 | + | |
| 769 | + | |
| 770 | + | |
| 771 | + | |
| 772 | + | |
| 773 | + | |
| 774 | + | |
| 775 | + | |
| 776 | + | |
| 777 | + | |
| 778 | + | |
741 | 779 | | |
742 | 780 | | |
743 | 781 | | |
| |||
0 commit comments