The .org TLD nameservers point to ns1 – ns4.opensuse.org as the authoritative nameservers for openSUSE.org. Appears that while ns2 and and ns3.opensuse.org are working, ns1 and ns4.opensuse.org return SERVFAIL when querying for openSUSE.org records. Your first sample log entry for lists.opensuse.org NS record was against ns4.opensuse.org (195.135.221.195) which returns SERVFAIL for your query. Problem is on openSUSE.org’s nameservers (not your end).
I’m unable to duplicate the second sample log message for SERVFAIL response for A record of 134.94.245.198.bb.barracudacentral.org . Your log indicates that the nameserver 3.13.7.25 (which is the authoritative nameserver blacklist-ns-az1.bci.aws.cudaops.com) returned a SERVFAIL for the request. The second sample log message may have been due to an anomaly on the authoritative nameserver. From: bind-users <bind-users-boun...@lists.isc.org> on behalf of Alex <mysqlstud...@gmail.com> Date: Saturday, November 26, 2022 at 9:39 AM To: bind-users@lists.isc.org <bind-users@lists.isc.org> Subject: lame-servers: SERVFAIL unexpected RCODE resolving CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe. Hi, Continuing in my quest to figure out why I'm seeing timeout issues from many of the same nameservers, I'm wondering if someone can help me identify the reason for these log entries: 26-Nov-2022 09:19:13.969 lame-servers: SERVFAIL unexpected RCODE resolving 'lists.opensuse.org/NS/IN<https://nam02.safelinks.protection.outlook.com/?url=http%3A%2F%2Flists.opensuse.org%2FNS%2FIN&data=05%7C01%7Crick.frey%40windstream.com%7C10262a839b59471b67aa08dacfc45bba%7C2567b4c1b0ed40f5aee358d7c5f3e2b2%7C0%7C0%7C638050739513352925%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=DE698kS1g5rgXqhgI4Vk%2F%2FOBvc5B2dmb3nUTzBXNl9U%3D&reserved=0>': 195.135.221.195#53 26-Nov-2022 10:02:46.437 lame-servers: SERVFAIL unexpected RCODE resolving '134.94.245.198.bb.barracudacentral.org/A/IN<https://nam02.safelinks.protection.outlook.com/?url=http%3A%2F%2F134.94.245.198.bb.barracudacentral.org%2FA%2FIN&data=05%7C01%7Crick.frey%40windstream.com%7C10262a839b59471b67aa08dacfc45bba%7C2567b4c1b0ed40f5aee358d7c5f3e2b2%7C0%7C0%7C638050739513352925%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=BNpl9x8nLnZ4vuiOeT0zZBJHahr%2BCrfwHJdSM%2B37ufs%3D&reserved=0>': 3.13.7.254#53 The vast majority of these types of entries are from the same nameservers as above. This is a mail server and at least the barracuda entry is a query to their blocklist service. Are others having problems with this barracuda service? I realize generally lame-servers entries can be ignored, but it's a bit concerning to me, given the large amount of similar entries we're seeing every day. It also resulted in zero other similar questions when searching for this error. Any ideas greatly appreciated. Thanks, Alex Sensitivity: Internal
-- 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
