[master] RPZ speedup (phase 2, multiple RPZ's)
3495. [func] Support multiple response-policy zones, while improving RPZ performance. [RT #32476]
This commit is contained in:
@@ -1,4 +1,4 @@
|
||||
; Copyright (C) 2011, 2012 Internet Systems Consortium, Inc. ("ISC")
|
||||
; Copyright (C) 2011-2013 Internet Systems Consortium, Inc. ("ISC")
|
||||
;
|
||||
; Permission to use, copy, modify, and/or distribute this software for any
|
||||
; purpose with or without fee is hereby granted, provided that the above
|
||||
@@ -12,7 +12,6 @@
|
||||
; OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
|
||||
; PERFORMANCE OF THIS SOFTWARE.
|
||||
|
||||
; $Id: base.db,v 1.6.4.1 2011/10/15 23:03:38 vjs Exp $
|
||||
|
||||
|
||||
; RPZ test
|
||||
@@ -40,3 +39,10 @@ ns A 10.53.0.3
|
||||
redirect A 127.0.0.1
|
||||
*.redirect A 127.0.0.1
|
||||
*.credirect CNAME google.com.
|
||||
|
||||
|
||||
; names in the RPZ TLDs that some say should not be rewritten.
|
||||
; This is not a bug, because any data leaked by writing 24.4.3.2.10.rpz-ip
|
||||
; (or whatever) is available by publishing "foo A 10.2.3.4" and then
|
||||
; resolving foo.
|
||||
32.3.2.1.127.rpz-ip CNAME walled.invalid.
|
||||
|
||||
Reference in New Issue
Block a user