using different IP

[Dave Henderson]

Gang,
    I have tried google groups to find the answer to this question, but keep getting answers on binding multiple IP addresses to a single nic (which I have already done).  I am trying to make BIND use one of the 3 IP's in use by a particular nic and it isn't the primary IP either (192.168.0.81).  The only post I found that remotely answered my question says to use the "listen-on" parameter (which I had already configured), but when I look in my logs to see whats going on (on the secondary server) when two of my zone files fail to transfer over, here is what I get:

Mar 24 09:57:39 localhost named[6227]: transfer of 'foo.com/IN' from 192.168.0.11#53: connected using 192.168.0.81#35134
Mar 24 09:57:39 localhost named[6227]: transfer of 'foo.com/IN' from 192.168.0.11#53: failed while receiving responses: REFUSED
Mar 24 09:57:39 localhost named[6227]: transfer of 'foo.com/IN' from 192.168.0.11#53: end of transfer


The IP address that should be in use is 192.168.0.31, not 192.168.0.81.  Also, this is a secondary server and receives the zone files for all the other zones configured, but seems to bomb on just two of them.  I have checked the configuration for both of those zones and they match what all the others have (their "allow-transfer" parameter is set to 192.168.0.31).  Also looking at the master bind server's logs I get the following:

Mar 24 22:55:08 localhost named[3020]: client 192.168.0.81#35136: zone transfer 'foo.com/IN' denied

Why would it be trying to send information to the .81 IP address and not the .31 address?  Here is a copy of the masters named.conf.options script:

acl internals { 192.168.0.31; };
//acl externals { 70.46.29.218; };
//acl masters { 192.168.0.11; };

options {
        allow-notify { 192.168.0.31; };
        directory "/var/cache/bind";
        query-source address * port 53;
        forwarders {
                65.32.5.74;
                65.32.5.75;
        };
        auth-nxdomain no;    # conform to RFC1035
}


Thanks,
Dave