Hi Mark, Thanks so much for your help. I will at least make an attempt to reach out to BestWestern with a summary of what you've discovered.
> 31-May-2023 17:00:51.990 query-errors: info: client @0x7f8d00a1b968 > 127.0.0.1#56239 (_dmarc.zoominfo.com): query failed (timed out) for _ > dmarc.zoominfo.com/IN/TXT at ../../../lib/ns/query.c:7779 > > 31-May-2023 17:00:52.172 query-errors: info: client @0x7f8d00de5168 > 127.0.0.1#30280 (travel-assets.com.fresh30.spameatingmonkey.net): query > failed (timed out) for travel-assets.com.fresh30.spameatingmonkey.net/IN/A > at ../../../lib/ns/query.c:7779 > > 31-May-2023 17:03:52.542 query-errors: client @0x7f53da961d68 > 68.195.111.45#50747 (31.57.89.167.bb.barracudacentral.org): query failed > (timed out) for 31.57.89.167.bb.barracudacentral.org/IN/A at > ../../../lib/ns/query.c:7779 > This is from a test server on a cable modem. Can you tell me if these problems could be caused by trying to run a DNS server on a cable connection? Is there something inherent about the way cable works that would prevent the ability to use a DNS server reliably? Perhaps these timeouts are due to retransmission errors? How can I determine this, or better identify the reason for the timeouts? Thanks, Alex
-- 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
