1. 04 Sep, 2018 1 commit
  2. 03 Sep, 2018 1 commit
  3. 31 Aug, 2018 7 commits
  4. 29 Aug, 2018 3 commits
  5. 28 Aug, 2018 12 commits
  6. 27 Aug, 2018 2 commits
  7. 25 Aug, 2018 1 commit
    • Michał Kępień's avatar
      Set "use-alt-transfer-source no;" in the "mirror" system test · a23162ab
      Michał Kępień authored
      Force ns3 to use a constant source address ( when sending
      transfer requests for the "initially-unavailable" zone to prevent
      failures of transfers not triggered by bin/tests/system/mirror/tests.sh
      from causing fallback to using a source address for which transfers of
      that zone are refused throughout the entire "mirror" system test since
      that might yield false positives.
  8. 24 Aug, 2018 2 commits
    • Michał Kępień's avatar
      Log a message when "ixfr-from-differences" is set for an inline-signed zone · 087157d1
      Michał Kępień authored
      For inline-signed zones, the value of "ixfr-from-differences" is
      hardcoded to:
        - "yes" for the raw version of the zone,
        - "no" for the signed version of the zone.
      In other words, any user-provided "ixfr-from-differences" setting is
      effectively ignored for an inline-signed zone.  Ensure the user is aware
      of that by adding a note to the ARM and logging a message when an
      "ixfr-from-differences" option is found at the zone level.
    • Michał Kępień's avatar
      Prevent a race in the "inline" system test · e36c869e
      Michał Kępień authored
      A short time window exists between logging the addition of an NSEC3PARAM
      record to a zone and committing it to the current version of the zone
      database.  If a query arrives during such a time window, an unsigned
      response will be returned.  One of the checks in the "inline" system
      test requires NSEC3 records to be present in an answer - that check
      would fail in the case described above.  Use rndc instead of log
      watching for checking whether zone signing and NSEC3 chain modifications
      are complete in order to prevent intermittent "inline" system test
  9. 23 Aug, 2018 4 commits
  10. 22 Aug, 2018 4 commits
    • Evan Hunt's avatar
    • Michał Kępień's avatar
      Fix reloading inline-signed zones · 54315839
      Michał Kępień authored
      While "rndc reload" causes dns_zone_asyncload() to be called for the
      signed version of an inline-signed zone, the subsequent zone_load() call
      causes the raw version to be reloaded from storage.  This means that
      DNS_ZONEFLG_LOADPENDING gets set for the signed version of the zone by
      dns_zone_asyncload() before the reload is attempted, but zone_postload()
      is only called for the raw version and thus DNS_ZONEFLG_LOADPENDING is
      cleared for the raw version, but not for the signed version.  This in
      turn prevents zone maintenance from happening for the signed version of
      the zone.
      Until commit 29b7efdd, this problem
      remained dormant because DNS_ZONEFLG_LOADPENDING was previously
      immediately, unconditionally cleared after zone loading was started
      (whereas it should only be cleared when zone loading is finished or an
      error occurs).  This behavior caused other issues [1] and thus had to be
      Fix reloading inline-signed zones by clearing DNS_ZONEFLG_LOADPENDING
      for the signed version of the zone once the raw version reload
      completes.  Take care not to clear it prematurely during initial zone
      load.  Also make sure that DNS_ZONEFLG_LOADPENDING gets cleared when
      zone_postload() encounters an error or returns early, to prevent other
      scenarios from resulting in the same problem.  Add comments aiming to
      help explain code flow.
      [1] see RT #47076
    • Michał Kępień's avatar
      Set DNS_JOURNALOPT_RESIGN when loading the secure journal for an inline-signed zone · 8db550c4
      Michał Kępień authored
      When an inline-signed zone is loaded, the master file for its signed
      version is loaded and then a rollforward of the journal for the signed
      version of the zone is performed.  If DNS_JOURNALOPT_RESIGN is not set
      during the latter phase, signatures loaded from the journal for the
      signed version of the zone will not be scheduled for refresh.  Fix the
      conditional expression determining which flags should be used for the
      dns_journal_rollforward() call so that DNS_JOURNALOPT_RESIGN is set when
      zone_postload() is called for the signed version of an inline-signed
      Extend bin/tests/system/stop.pl so that it can use "rndc halt" instead
      of "rndc stop" as the former allows master file flushing upon shutdown
      to be suppressed.
    • Michał Kępień's avatar
      Do not treat a referral with a non-empty ANSWER section as an error · 24b9ec55
      Michał Kępień authored
      As part of resquery_response() refactoring [1], a goto statement was
      replaced [2] with a call to a new function - originally called
      rctx_delegation(), now folded into rctx_answer_none() - extracted from
      existing code.  However, one call site of that refactored function does
      not reset the "result" variable, causing a referral with a non-empty
      ANSWER section to be inadvertently treated as an error, which prevents
      resolution of names reliant on servers sending such responses.  Fix by
      resetting the "result" variable to ISC_R_SUCCESS when a response
      containing a non-empty ANSWER section can be treated as a delegation.
      [1] see RT #45362
      [2] see commit e1380a16741a3b4a57e54d7a9ce09dd12691522f
  11. 16 Aug, 2018 2 commits
  12. 14 Aug, 2018 1 commit