I get warning messages like "zone example.com/IN: refresh: failure trying master 220.127.116.11#53: timed out".
- Updated on 21 Dec 2016
- 1 minute to read
Check that you can make UDP queries from the slave to the master
dig +norec example.com soa @18.104.22.168
You could be generating queries faster than the slave can cope with. One simple strategy would be to lower the serial query rate.
serial-query-rate 5; // default 20
Changes to serial-query-rate and other configuration options relating to zone refresh
BIND has been updated to separate the rate limiting controlled originally by the serial-query-rate into several options so that SOA refresh queries and zone update notifications can be independently controlled. For more information see serial-query-rate, notify-rate and startup-notify-rate: how they impact zone transfers in different versions of BIND
DNS System Administrators who would like to learn more about tuning their Master and Slave servers more effectively may be interested in reading: Tuning your BIND configuration effectively for zone transfers (particularly with many frequently-updated zones)
© 2001-2018 Internet Systems Consortium For assistance with problems and questions for which you have not been able to find an answer in our Knowledge Base, we recommend searching our community mailing list archives and/or posting your question there (you will need to register there first for your posts to be accepted). The bind-users and the dhcp-users lists particularly have a long-standing and active membership. ISC relies on the financial support of the community to fund the development of its open source software products. If you would like to support future product evolution and maintenance as well having peace of mind knowing that our team of experts are poised to provide you with individual technical assistance whenever you call upon them, then please consider our Professional Subscription Support services - details can be found on our main website.