I have a DNS master and two DNS Slaves. The master has the allow-transfer setup as

allow-transfer { ip.address; ip .address; };

When I made a zone change and reloaded named, I did not see the server try to send any updates for the zone to the second server, which is a new one on FC10, while it did send the update to the other slave. I also noticed that when I first got the new server online, the zone transfers didn't happen until I restarted named on the new server, then all the zones updated. I swapped the ip's in named.conf so the new server address was first, changed the zone file serial in question so it updated, and reloaded named, and again, did not see the server try to update the new server, in fact I saw nothing except the update to the old server. Here are the options on the new server.

options {
listen-on port 53 { any; };
listen-on-v6 port 53 { ::1; };
directory "/var/named";
dump-file "/var/named/data/cache_dump.db";
statistics-file "/var/named/data/named_stats.txt";
memstatistics-file "/var/named/data/named_mem_stats.txt";
allow-query { any; };
recursion yes;


As far as name resolution, the server is working fine, I can resolve against it both for dns and nslookup. This appears to be my only problem, sending updated zones to it from the master.

Check the master's logs, to see if it sends notifies to the 2nd slave and that in turn receives them. Also look at the serial on the secondary to see if it's greater than the one on the master.

I did both, on the master I ran tail -f /var/log/messages, I see the notify go out to the old server, but not to the new one. The serial on the new server is 20080xxxx the master serial is 20090xxxx. What I did notice the first time I brought the server up to synch with the master, none of the zone transfers occurred until I did a restart of named on the new server. I am thinking I have something incorrect somewhere on the master.

Make sure that you have added the new secondary dns in the zone file of the domain(s) that your master is authoritative for. E.g:

Well now this is odd. I added the NS record, and I did see our primary zone transfer, so then I upped the serial on the other zone, and it did not transfer, but here is the odd thing, some time since I opened this thread and now, the zone file did get transferred. I will give it a day or so and then check the files again and try another zone update and see what happens. For the most part, it looks like it may have been the NS record that was missing.

Its working now, but taking nearly 2 hours before the zone transfer occurs. The other server is immediate. Could this be OS related? The other server is FC6, this is FC10. The master is RH9.

The underlying OS has nothing to do with bind behavior. 2h is most likely the default retry value in your zone file. Since you didn't post the named.conf of your master, maybe you have to add the new slave in a "notify" statement for your zone.
You can do more checking by enabling logging in the slave, increase the serial in master, reload bind and look at both logs to see if a notify is send and received respectively.