policy.rpz: various fixes (!1016) · 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 rpz-warnings into master 4 years ago

Jun 30, 2020
- NEWS: describe the RPZ fixes · 46a907fa
  Vladimír Čunát authored 4 years ago
  
  Verified
  
  46a907fa
- policy.rpz: support local data with larger RRsets · 9ecf0222
  Vladimír Čunát authored 4 years ago
  
  Verified
  
  9ecf0222
- tests check_answer(): support checking RDATA · 9657081d
  Vladimír Čunát authored 4 years ago
  
  Also allow using empty set as an alternative to NODATA pseudo-RCODE, and migrate RPZ tests to this merged function.
  Verified
  
  9657081d
- policy.ANSWER: allow multiple RRs · 7e472204
  Vladimír Čunát authored 4 years ago
  
  ... by allowing .rdata to be a table. Larger RRsets seem useful.
  Verified
  
  7e472204
- policy.rpz: fix $ORIGIN-related handling · f78fea28
  Vladimír Čunát authored 4 years ago
  
  - use parser-detected $ORIGIN instead of looking at SOA owner - skip records outside $ORIGIN (and warn) instead of nesting them - simplify a bit, and tweak warnings
  Verified
  
  f78fea28
- policy.rpz: don't warn on NS and SOA records · 9a96d514
  Vladimír Čunát authored 4 years ago
  
  Also utilize table indexing. This was a "regression" from extending RPZ support in 5.1.0. NS and SOA are even mandatory, as RPZ is supposed to be a valid zone: https://tools.ietf.org/html/draft-ietf-dnsop-dns-rpz-00#section-2
  Verified
  
  9a96d514