Selective forwarders not working

[Kevin Darcy]

There is a subtle interaction between delegation and selective 
forwarding in BIND: selective forwarding only applies to *zones*, not 
*domains*, so you need to make sure that what you're trying to forward 
is properly delegated from its parent zone.

                                                                         
                                    - Kevin

Junice wrote:

>Hi,
>    I have also turned on the debug and below is the traces :
>req:nlookup(xxxxxx.com) id .. type=1 class=1 rc=3
>ns_req:answer ->[127.0.0.1]:... fd=20 id=... size=81 rc=3
>
>What i rx from the nslookup result is a very fast response of error
>message "non-existent domain". From the traces as above, there is no
>Forwarding done but just very prompt responce of "non-existent"
>domain.
>Any clue on what could be the problem ? I have also added the "forward
>only" in the xxxxxx.com forward zone but again with the same result.
>
>Thanks in advance.
>
>
>
>Barry Margolin <barmar at alum.mit.edu> wrote in message news:<c80i9p$10gv$1 at sf1.isc.org>...
>  
>
>>In article <c80dbu$ras$1 at sf1.isc.org>, sssia at cyberway.com.sg (Junice) 
>>wrote:
>>
>>    
>>
>>>Hi,
>>>   I have problem in configuring the internal DNS server to perform
>>>specific forwarding. Below describe the internal DNS configuration
>>>
>>>In my internal DNS server, I have following being configured :
>>>
>>>....
>>>options {
>>>         ....
>>>         forwarders {
>>>             200.200.200.200;
>>>             201.201.201.201;
>>>             };
>>>         forward only;
>>>         ....
>>>zone "xxxxx.com" {
>>>     type forward;
>>>     forwarders { 2.2.2.2; };
>>>      };
>>>
>>>
>>>I have no problem with the global forwarders where I use it for
>>>forwarding query to Internet domain names. However , when I recently
>>>try to add selective forwarders to forward any query of xxxxx.com to
>>>be forwarded to 2.2.2.2 instead of the global forwarders
>>>200.200.200.200,201.201.201.201, the selective forwarded fail to work.
>>>
>>>Does anyone know where the problem is ? Can I override global
>>>forwarder with a a selective forwarder like the way I defined above ?
>>>I am using Bind 8.3.4.
>>>      
>>>
>>What you tried is supposed to work, and it looks correct to me.  Have 
>>you checked your log?  Have you tried turning on tracing to see what 
>>it's doing?
>>    
>>
>
>
>
>
>  
>