1. 02 Jan, 2013 1 commit
  2. 01 Jan, 2013 1 commit
  3. 07 Dec, 2012 1 commit
  4. 06 Dec, 2012 1 commit
    • Evan Hunt's avatar
      [master] multiple-dlz/dlz-nxdomain · 2b8bed66
      Evan Hunt authored
      3432.	[func]		Multiple DLZ databases can now be configured.
      			DLZ databases are searched in the order configured,
      			unless set to "search no", in which case a
      			zone can be configured to be retrieved from a
      			particular DLZ database by using a "dlz <name>"
      			option in the zone statement.  DLZ databases can
      			support type "master" and "redirect" zones.
      			[RT #27597]
      2b8bed66
  5. 26 Oct, 2012 1 commit
  6. 02 Oct, 2012 2 commits
  7. 17 Aug, 2012 1 commit
  8. 15 Aug, 2012 2 commits
  9. 14 Aug, 2012 1 commit
  10. 11 Aug, 2012 1 commit
  11. 29 Jun, 2012 3 commits
  12. 10 Mar, 2012 1 commit
  13. 07 Mar, 2012 1 commit
  14. 05 Mar, 2012 3 commits
  15. 04 Mar, 2012 2 commits
    • Evan Hunt's avatar
      created · 43cf20e3
      Evan Hunt authored
      43cf20e3
    • Evan Hunt's avatar
      checkpoint: multiple-DLZ functionality · 95450171
      Evan Hunt authored
       - multiple DLZ's can be specified, including multiple DLZ's using
         the same driver; e.g., two different back-ends both loaded by the
         dlopen driver
       - new "search" option can be specified in a DLZ indicating whether
         this DLZ database should be searched for unknown zones.  The
         default is "yes".  If "no", then the zone can only be found by
         named if it's registered in the zone table, which happens if the
         zone is configured for dynamic updates, or if "dlz <dlzname>" is
         specified in the zone statement. (The latter functionality is
         incomplete in this commit).
      95450171
  16. 07 Nov, 2011 1 commit
  17. 08 May, 2011 1 commit
  18. 07 May, 2011 2 commits
  19. 05 May, 2011 2 commits
  20. 02 Jun, 2010 2 commits
  21. 19 Jun, 2007 1 commit
  22. 18 Jun, 2007 1 commit
  23. 23 Jun, 2005 1 commit