1. 25 Jan, 2019 7 commits
  2. 24 Jan, 2019 8 commits
  3. 23 Jan, 2019 4 commits
  4. 22 Jan, 2019 2 commits
  5. 21 Jan, 2019 4 commits
  6. 18 Jan, 2019 12 commits
  7. 16 Jan, 2019 3 commits
    • Evan Hunt's avatar
      Merge branch '752-disable-forwarders-when-priming' into 'master' · 4a827494
      Evan Hunt authored
      If possible don't use forwarders when priming the resolver.
      
      Closes #752
      
      See merge request !1296
      4a827494
    • 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.
      b49310ac
    • Mark Andrews's avatar
      Merge branch 'pkcs11-pubattr-check' into 'master' · a97a63ad
      Mark Andrews authored
      Make sure null atributes are never used
      
      See merge request !1353
      a97a63ad