when one view doesn't have the zone

[pyh at mail.nsbeta.info]

Mark Andrews writes: 

> 
> In message <20110121024745.BCD2E2CF86 at mail.nsbeta.info>, pyh at mail.nsbeta.info w
> rites:
>> 
>> Hello,  
>> 
>> My named.conf looks as:
>>  ----------------------------------
>> view "view_a" {
>>     match-clients {
>>         IP_ADDR_A;
>>     };
>>     zone "test.com" {
>>         type master;
>>         file "test.com.a.db";
>>     };
>> };  
>> 
>> view "view_b" {
>>     match-clients {
>>         IP_ADDR_B;
>>     };
>>     # doesn't have test.com zone here
>> };  
>> 
>> view "view_c" {
>>     match-clients {
>>         IP_ADDR_C;
>>     };
>>     zone "test.com" {
>>         type master;
>>         file "test.com.c.db";
>>     };
>> };
>>  ----------------------------------  
>> 
>> As you see, test.com doesn't have a zone in view_b.
>> But view_b should be there because other zones may need it.  
>> 
>> So under this case, when clients from ISP_ADDR_B query for test.com, they 
>> will get nothing.  
>> 
>> How can I resolve this problem? Thanks in advance. 
> 
> Sometimes you have to workout what you want the answer to be before
> people can tell you how to achieve it.  This is one of those times. 
> 
> What do you want the clients that match view_b to see? 
> 

Thanks for pointing me.
In  fact I want to the clients that match view_b to fall into the default 
view, say it's view_c. 

Regards.