I am running bind 9.16.19 on two FreeBSD 13-STABLE instances. The master is on a Digital Ocean droplet and works fine. The slave is hosted on physical machine here in our offices.
This has always worked flawlessly until recently. Periodically, the slave refuses to resolve names like 'git.freebsd.org' and we have to restart bind on the slave to get it working correctly again. Rather than using cron to restart bind every hour (!), we'd like to get to the root of the problem. The slave machine is at the end of a Comcast Business pipe and their execrable security edge garbage may be implicated. We could use some help on an approach to debugging this. Having never had significant bind problems over 20 years of use, we literally have no named debugging experience... TIA, -- ---------------------------------------------------------------------------- Tim Daneliuk tun...@tundraware.com PGP Key: http://www.tundraware.com/PGP/ _______________________________________________ Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list ISC funds the development of this software with paid support subscriptions. Contact us at https://www.isc.org/contact/ for more information. bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
