[Q] BIND secondary on RedHat 7.1

[Marc.Thach at radianz.com]

Pawprint,
when you nslookup do you set the server to be 127.0.0.1 or does it actually
query the first server in the resolv.conf (your primary).  If the latter is
the case, then what evidence do you have that the secondary BIND is runnng
and listening?
Do you have an allow-transfer clause on the master?  Does your router allow
your secondary through it?
rgds
Marc TXK



                                                                                                                    
                    pawprint at NOSPAM.                                                                                
                    neo.rr.com              To:     comp-protocols-dns-bind at moderators.isc.org                      
                    (Homer the              cc:                                                                     
                    Prairie Dog)            Subject:     Re: [Q] BIND secondary on RedHat 7.1                       
                    Sent by:                                                                                        
                    bind-users-bounc                                                                                
                    e at isc.org                                                                                       
                                                                                                                    
                                                                                                                    
                    10/10/2001 03:24                                                                                
                                                                                                                    
                                                                                                                    




All the machines that need to do queries are on 192.168.1.x

I do have full internet activity, and my forwarders do answer queries
faster,
on average, than my primary nameserver can resolve them - for queries
outside
the 192.168.1.x zone.

What I am still looking for an answer to is why my secondary RedHat
nameserver
won't answer any queries from any machine.

In article <9pvr60$at7 at pub3.rc.vix.com>, Kevin Darcy
<kcd at daimlerchrysler.com>
wrote:
>
>What addresses do these "other machines" have? You're configured (the
>allow-query clause) to only allow queries from 192.168.1/24 and
127.0.0/24.
>
>BTW, you shouldn't be specifying "forward first" unless you have full
Internet
>connectivity and your forwarders answer queries faster on average than
your
>nameserver can resolve them itself.
>
>
>- Kevin
>
>pawprint at NOSPAM.neo.rr.com wrote:
>
>> I have a RedHat 7.1 server set up and am trying to configure BIND to be
a
>> secondary DNS server for my internal domain while also forwarding
queries for
>> outside servers to my ISPs name servers. If I use nslookup on the
>> RedHat server everything appears to be working fine, but the server does
not
>> answer queries from other machines.  Named is starting up fine, appears
to be
>> working fine from the server console, it just doesn't answer queries
from
>> other machines.
>>
>> My primary nameserver is ISHMAEL at 192.168.1.2
>> The RedHat secondary is STARBUCK at 192.168.1.3 (this is the one that
won't
>> answer queries).
>> The internal domain is savonarola.com
>>
>> my named.conf and resolv.conf files are below
>>
>> ## named.conf - configuration for bind
>> #
>> # Generated automatically by bindconf, alchemist et al.
>>
>> options {
>>         directory "/var/named/";
>>         forward first;
>>         forwarders {65.24.0.167; 65.24.0.166;};
>>         fetch-glue no;
>>         recursion no;
>>         allow-query { 192.168.1/24; 127.0.0/24; };
>>         allow-transfer { 192.168.1.2; };
>>         transfer-format many-answers;
>> };
>>
>> zone  "." {
>>         type hint;
>>         file  "named.ca";
>> };
>>
>> zone  "0.0.127.in-addr.arpa" {
>>         type master;
>>         file  "0.0.127.in-addr.arpa.zone";
>> };
>>
>> zone  "localhost" {
>>         type master;
>>         file  "localhost.zone";
>> };
>>
>> zone  "savonarola.com" {
>>         type slave;
>>         file  "savonarola.com.zone";
>>         masters { 192.168.1.2; };
>> };
>>
>> zone "192.168.1.in-addr.arpa" in {
>>         type slave
>>         file "db.192.168.1";
>>         masters { 192.168.1.2; };
>> };
>>
>> this is the resolv.conf file
>>
>> search savonarola.com neo.rr.com rr.com
>> nameserver 192.168.1.2
>> nameserver 65.24.0.166
>> nameserver 65.24.0.167
>
>
>
>
>