1. 22 Feb, 2019 2 commits
  2. 21 Feb, 2019 5 commits
  3. 20 Feb, 2019 1 commit
  4. 19 Feb, 2019 2 commits
  5. 18 Feb, 2019 1 commit
    • Tony Finch's avatar
      Improve dnssec-keymgr manual · 7ee56e2a
      Tony Finch authored
      Illustrate the syntax for the policy options, with semicolons.
      Explicitly mention the "default" policy.
      Fix a few typos and remove some redundant wording.
  6. 14 Feb, 2019 1 commit
  7. 10 Feb, 2019 1 commit
  8. 08 Feb, 2019 2 commits
  9. 07 Feb, 2019 2 commits
  10. 06 Feb, 2019 4 commits
  11. 31 Jan, 2019 5 commits
  12. 30 Jan, 2019 2 commits
  13. 29 Jan, 2019 1 commit
  14. 25 Jan, 2019 2 commits
  15. 24 Jan, 2019 2 commits
  16. 23 Jan, 2019 1 commit
  17. 22 Jan, 2019 1 commit
  18. 16 Jan, 2019 5 commits
    • Witold Krecicki's avatar
      If possible don't use forwarders when priming the resolver. · b49310ac
      Witold Krecicki authored
      If we try to fetch a record from cache and need to look into
      hints database we assume that the resolver is not primed and
      start dns_resolver_prime(). Priming query is supposed to return
      NSes for "." in ANSWER section and glue records for them in
      ADDITIONAL section, so that we can fill that info in 'regular'
      cache and not use hints db anymore.
      However, if we're using a forwarder the priming query goes through
      it, and if it's configured to return minimal answers we won't get
      the addresses of root servers in ADDITIONAL section. Since the
      only records for root servers we have are in hints database we'll
      try to prime the resolver with every single query.
      This patch adds a DNS_FETCHOPT_NOFORWARD flag which avoids using
      forwarders if possible (that is if we have forward-first policy).
      Using this flag on priming fetch fixes the problem as we get the
      proper glue. With forward-only policy the problem is non-existent,
      as we'll never ask for root server addresses because we'll never
      have a need to query them.
      Also added a test to confirm priming queries are not forwarded.
    • Witold Krecicki's avatar
      When a forwarder fails and we're not in a forward-only mode we · cfa2804e
      Witold Krecicki authored
      go back to regular resolution. When this happens the fetch timer is
      already running, and we might end up in a situation where we we create
      a fetch for qname-minimized query and after that the timer is triggered
      and the query is retried (fctx_try) - which causes relaunching of
      qname-minimization fetch - and since we already have a qmin fetch
      for this fctx - assertion failure.
      This fix stops the timer when doing qname minimization - qmin fetch
      internal timer should take care of all the possible timeouts.
    • Michał Kępień's avatar
      Add CHANGES entry · 5d37c910
      Michał Kępień authored
      5137.	[func]		named now logs messages whenever a mirror zone becomes
      			usable or unusable for resolution purposes. [GL #818]
    • Evan Hunt's avatar
      CHANGES · 03ab07c9
      Evan Hunt authored
    • Mark Andrews's avatar
      use smt_pause instead of pause on sparc · 2be55f5c
      Mark Andrews authored