strange errors / named stops responding

[Federico Bockel]

Hi, i have 3 ns, 1 primary, 2 slaves, running Bind 9.1.1 on solaris 7.
This is the problem.
 
I get this two errors on log:
 
Apr 18 00:24:17.298 general: warning: dns_master_load:
slave/macrosa.com.ar:10: $TTL 3306160128 > MAXTTL, setting $TTL to 0
Apr 18 00:24:26.515 general: info: running
 
After that, all the zones ~2000, got a refresh_callback, this happens
everytime i start the named.
The thing is, that the 3 ns are in the same vlan, with no firewall or
anything blocking the communication on port 53,
so i dont know why it says time out for 200.45.0.114 (the primary) (the
slaves have other primarys for some zones, these zones also got this
error)
 
Apr 18 00:24:45.090 general: info: refresh_callback: zone
energia.com.ar/IN: failure for 200.45.0.114#53: timed out
Apr 18 00:24:45.610 general: info: refresh_callback: zone
grupotradis.com.ar/IN: failure for 200.45.0.114#53: timed out
Apr 18 00:24:45.610 general: info: refresh_callback: zone
travelpass.com.ar/IN: failure for 200.45.0.114#53: timed out
Apr 18 00:24:45.610 general: info: refresh_callback: zone
agf-allianz.com.ar/IN: failure for 200.45.0.114#53: timed out
 
But, when i change a zone, the serial, and hup named on primary works ok
replicating the zone changes, so, what is this problem?
 
This week, a lot of times happened that the service stops responding
querys and i have to do a kill -9 and start it again cause wont respond
with a HUP i dont know if this is related to the large 
volume of errors (refresh_callback) sended to the log file and this
somehow slowing the service performance, and taking it to a still.

Any help on this problems, specially any idea why the named stops
responding, if it is related to this, or not, would be great!
Thanks!
 
 Federico Bockel