On Jun 23, 2009, at 11:57 PM, Chris Buxton wrote:
No, we have not. However, it appears to be related to the port being idle for some time. Servers that use their TCP port more frequently, usually due to having lots of zone updates that need to be replicated to slaves, don't appear to be affected. You might try creating a cron job that digs against the TCP port every 5 minutes to try to keep the port "active" and prevent it from gong deaf.
If I make a schedule script, any suggestions on which is the best host to query to keep this port open? Would dig my.ns.example.com +tcp solve it, or should I hit one of the roots, with them also being highly available as well?
-- Scott * If you contact me off list replace talklists@ with scott@ * _______________________________________________ bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
