BIND 9.3.2 problems

[Paul Amaral]

Hi,

I'm wondering if anyone on this list can help me figure out the following 2
problems.

I'm getting ready to replace a secondary server using bind 9.2.3 with
another server using bind 9.3.2.
The primary server is also using bind 9.2.3.

The 1st problem is whenever I change the serial on a zone on the primary
server and then rndc reload it. The changes are instantly known to my old
secondary server using bind 9.2.3 but not to my replacement server using
bind 9.3.2.
I have to go into that server and issue rndc reload zonename for the serial
to change. Also whenever using rndc reload I get
zone refresh queued but it does change the serial.

I have all my name servers set to allow axfr's from all of my network ips.
Heres basically the conf im using:

options {

        // "/" is in /chroot/named <--- chroot jail. p.a

        directory "/";
        pid-file "/var/run/named.pid";
        statistics-file "/var/run/named.stats";

        transfers-in 200; < ------ are these causing the problem ?
        transfers-per-ns 150;

        // xfers from this server to another
        // transfers-out 20;

        allow-transfer { our-ips; };

        /*
         * If there is a firewall between you and nameservers you want
         * to talk to, you might need to uncomment the query-source
         * directive below.  Previous versions of BIND always asked
         * questions using port 53, but BIND 8.1 uses an unprivileged
         * port by default.
         */

        // query-source address * port 53;

        };

Aside form that 1st  issue I get the following error from bind "obsolete
setsocketopt SO_BSDCOMPAT" is this something to worry about ?

Thanks,
 
P