bind-9.5.1-1.P1 -- identicle zone listing and data file in different views, but doesn't work

Brian Neu proclivity76 at yahoo.com
Tue Mar 10 05:53:03 UTC 2009


Been looking at this for hours and can't figure it out. Views without recursion don't return a response.  I don't know what I'm doing wrong.  Setting "recursion yes" allows the zone to respond.

Sorry if this format is ugly.

Ideas?

Thanks!





>>>>>>named.conf

view "internal"
{
        match-clients           { !192.168.184.44; !192.168.184.46; franklin_way_nets; localnets; localhost; };
        match-destinations      { !192.168.184.43; !192.168.184.45; any;};
        recursion yes;
        include "/etc/named.root.hints";

    zone "128/27.168.193.66.in-addr.arpa" {
        type master;
        file "66.193.168.0.rev.db";
        allow-query { any; };
        allow-transfer { slaves; };
    };
<snip>


view    "comcast"
{
        match-clients           { any; };
        match-destinations      { 192.168.184.43; };

        recursion yes;
        include "/etc/named.root.hints";

    zone "128/27.168.193.66.in-addr.arpa" {
        type master;
        file "66.193.168.0.rev.comcast.db";
        allow-query { any; };
        allow-transfer { slaves; };
    };

<snip>



>/var/log/messages
Mar  9 17:03:57 w1 named[14663]: zone 128/27.168.193.66.in-addr.arpa/IN/internal: loaded serial 2008120901
Mar  9 17:03:58 w1 named[14663]: zone 128/27.168.193.66.in-addr.arpa/IN/timewarner: loaded serial 2008120901
Mar  9 17:03:58 w1 named[14663]: zone 128/27.168.193.66.in-addr.arpa/IN/comcast: loaded serial 2008120901


>named.run
zone 128/27.168.193.66.in-addr.arpa/IN/comcast: starting load
zone 128/27.168.193.66.in-addr.arpa/IN/comcast: number of nodes in database: 31
no journal file, but that's OK
zone 128/27.168.193.66.in-addr.arpa/IN/comcast: journal rollforward completed successfully: no journal
zone 128/27.168.193.66.in-addr.arpa/IN/comcast: loaded
zone 128/27.168.193.66.in-addr.arpa/IN/comcast: loaded serial 2008120901


>named.run
client 67.35.22.236#47252: UDP request
client 67.35.22.236#47252: view comcast: using view 'comcast'
client 67.35.22.236#47252: view comcast: request is not signed
client 67.35.22.236#47252: view comcast: recursion not available
client 67.35.22.236#47252: view comcast: query
client 67.35.22.236#47252: view comcast: query (cache) '130.168.193.66.in-addr.arpa/PTR/IN' approved
client 67.35.22.236#47252: view comcast: send
client 67.35.22.236#47252: view comcast: sendto
client 67.35.22.236#47252: view comcast: senddone
client 67.35.22.236#47252: view comcast: next
client 67.35.22.236#47252: view comcast: endrequest
client @0xb589d008: udprecv

client @0xb5c87008: udprecv
client 192.168.186.6#4399: UDP request
client 192.168.186.6#4399: view comcast: using view 'comcast'
client 192.168.186.6#4399: view comcast: request is not signed
client 192.168.186.6#4399: view comcast: recursion available
client 192.168.186.6#4399: view comcast: query
client 192.168.186.6#4399: view comcast: query (cache) '130.168.193.66.in-addr.arpa/PTR/IN' approved
client 192.168.186.6#4399: view comcast: query '130.128/27.168.193.66.in-addr.arpa/PTR/IN' approved
client 192.168.186.6#4399: view comcast: send
client 192.168.186.6#4399: view comcast: sendto
client 192.168.186.6#4399: view comcast: senddone
client 192.168.186.6#4399: view comcast: next
client 192.168.186.6#4399: view comcast: endrequest






More information about the bind-users mailing list