Hi, I'm using bind-9.18.15 on fedora37 and I'm trying to understand and troubleshoot some errors I'm receiving in the debug logs:
31-May-2023 16:58:11.399 query-errors: info: client @0x7f8d18203b68 127.0.0.1#56268 (bounce.bwnews.bestwestern.com): query failed (SERVFAIL) for bounce.bwnews.bestwestern.com/IN/NS at ../../../lib/ns/query.c:7060 31-May-2023 16:58:11.536 query-errors: info: client @0x7f8d00a1d568 127.0.0.1#38026 (email.bestwesternrewards.com): query failed (SERVFAIL) for email.bestwesternrewards.com/IN/NS at ../../../lib/ns/query.c:7060 31-May-2023 17:12:22.905 query-errors: client @0x7f53d920e368 68.195.111.45#54508 (_dmarc.email.bestwesternrewards.com): query failed (SERVFAIL) for _dmarc.email.bestwesternrewards.com/IN/TXT at ../../../lib/ns/query.c:7060 31-May-2023 17:12:22.921 query-errors: client @0x7f53d91aeb68 68.195.111.45#54508 (mail8140.bwnews.bestwestern.com): query failed (SERVFAIL) for mail8140.bwnews.bestwestern.com/IN/TXT at ../../../lib/ns/query.c:7060 31-May-2023 17:12:22.928 query-errors: client @0x7f53da5deb68 68.195.111.45#53653 (bounce.bwnews.bestwestern.com): query failed (SERVFAIL) for bounce.bwnews.bestwestern.com/IN/TXT at ../../../lib/ns/query.c:7060 Is Best Western actually having such DNS problems? Even just a simple "host" command shows something is wrong: $ host mail8140.bwnews.bestwestern.com mail8140.bwnews.bestwestern.com has address 129.41.76.129 Host mail8140.bwnews.bestwestern.com not found: 2(SERVFAIL) mail8140.bwnews.bestwestern.com mail is handled by 5 mail8140.bwnews.bestwestern.com. On another server, I'm receiving a bit more information: 31-May-2023 17:13:28.845 lame-servers: FORMERR resolving ' mail8140.bwnews.bestwestern.com/AAAA/IN': 205.251.194.123#53 31-May-2023 17:13:28.845 query-errors: client @0x7f655c820168 127.0.0.1#50563 (mail8140.bwnews.bestwestern.com): query failed (failure) for mail8140.bwnews.bestwestern.com/IN/AAAA at ../../../lib/ns/query.c:7779 What is the impact of these messages? I'm also receiving many timeout problems. 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 I think the last two occur on multiple servers, leading me to believe they actually have a problem? Barracuda requires that you register your IP with them, and I've done that, but other queries with them work just fine, even from servers that aren't registered. Could this be a bind tuning problem? Neither server where I ran these tests are having resource issues that I know of. Any ideas on how to troubleshoot these to confirm it's not a problem with my own server would be greatly appreciated. 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
