Opened 11 years ago
Closed 11 years ago
#6 closed defect (fixed)
Handle incosistent NSEC3 records within zone (removal/insertion by zone owner)
| Reported by: | wander | Owned by: | wander |
|---|---|---|---|
| Priority: | must-have | Component: | crawler |
| Keywords: | Cc: |
Description
In phase II of crawling larger zones the internal NSEC3 database becomes inconsistent when zone owner removes or inserts domains. Crawler should be able to handle this and put database into a clean state.
No longer existing NSEC3 hashes can be marked as historic or so but shouldn't be wiped.
Change History (3)
comment:1 Changed 11 years ago by
| Priority: | important → must-have |
|---|
comment:2 Changed 11 years ago by
| Owner: | set to wander |
|---|
comment:3 Changed 11 years ago by
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
Note: See
TracTickets for help on using
tickets.
(In [385]) finished handling of inconsistent data from server (not from db) and marking old NSEC3 records as obsolete
closes #6