Named ignoring forward-only zones?

[Jeff Laine]

On Thu, Jun 04, 2009 at 11:53:38AM -0500, Kirk Strauser wrote:
> For some reason, BIND 9 (FreeBSD 7.2-RELEASE) isn't properly forwarding 
> queries.  A snippet of named.conf:
> 
> acl clients {
>         localnets;
>         localhost;
>         ::1;      
>         10.45.12/19;
> };                         
> 
> view "internal" {
>         match-clients { clients; };
>         zone "5.0.10.in-addr.arpa" {
>                 type forward;
>                 forward only;
>                 forwarders { 10.0.5.16; };
>         };
> };
> 
> 
> Now, I can query the forwarder directly to get the right answer:
> 
> $ dig +noall +answer -t ptr -x 10.0.5.16 @10.0.5.16
> 16.5.0.10.in-addr.arpa. 86400   IN      PTR     kanga.honeypot.net.
> 
> But I can't get the same from named:
> 
> $ dig -t ptr -x 10.0.5.16
> 
> ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 56485
> ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
> 
> ;; QUESTION SECTION:
> ;16.5.0.10.in-addr.arpa.                IN      PTR
> 
> ;; AUTHORITY SECTION:
> 10.in-addr.arpa.        10800   IN      SOA     10.in-addr.arpa. 
> nobody.localhost. 42 86400 43200 604800 10800
> 
> So, why isn't named directing that query to the configured forwarder?  I'm 
> 99.9% certain this has been working recently.


Hi, Kirk.

I had the similar issue with forward type zones yesterday. 
Though I'm not quite sure, but it started to work after I put 127.0.0.1 
to /etc/resolv.conf on our bind server.


My named.conf entries look like this:

...
zone "need2.frwd.zone" {
        type forward;
        forward only;
        forwarders { 10.xx.xx.xx; 10.xx.xx.yy; };
};

zone "10.in-addr.arpa" {
        type forward;
        forward only;
        forwarders { 10.xx.xx.xx; 10.xx.xx.yy; };
};
...



-- 
Best regards,
Jeff

| "Nobody wants to say how this works.	|
|  Maybe nobody knows ..."		|
|  			Xorg.conf(5)	|