Re: match-recursive-only vs configured zones

2009-05-19 Thread Chris Buxton
On May 19, 2009, at 10:50 AM, Matus UHLAR - fantomas wrote: On May 19, 2009, at 9:45 AM, Matus UHLAR - fantomas wrote: I'd like to know how does match-recurtsive-only view interact with configured zones. On 19.05.09 10:25, Chris Buxton wrote: The order of views matters. The first one matched,

Re: match-recursive-only vs configured zones

2009-05-19 Thread Matus UHLAR - fantomas
> On May 19, 2009, at 9:45 AM, Matus UHLAR - fantomas wrote: >> I'd like to know how does match-recurtsive-only view interact with >> configured zones. On 19.05.09 10:25, Chris Buxton wrote: > The order of views matters. The first one matched, wins. > > Let's suppose you have a config along these

Re: match-recursive-only vs configured zones

2009-05-19 Thread Chris Buxton
On May 19, 2009, at 9:45 AM, Matus UHLAR - fantomas wrote: Hello, I'd like to know how does match-recurtsive-only view interact with configured zones. The order of views matters. The first one matched, wins. Let's suppose you have a config along these lines: view "resolver" { match-

match-recursive-only vs configured zones

2009-05-19 Thread Matus UHLAR - fantomas
Hello, I'd like to know how does match-recurtsive-only view interact with configured zones. When a zone is configured, clients accessing it are not recursive, unless it's forward (maybe stub?) zone... when I configure all zones in one view, and create other view using match-recursive-only, will