From: "Steven Levine" Received: from [192.168.100.201] (HELO mail.2rosenthals.com) by 2rosenthals.com (CommuniGate Pro SMTP 5.4.10) with ESMTPS id 7173193 for ecs-isp@2rosenthals.com; Sun, 21 May 2023 12:42:41 -0400 Received: from secmgr-va.randr ([192.168.200.201]:45064 helo=mail2.2rosenthals.com) by mail.2rosenthals.com with esmtp (Exim 4.96) (envelope-from ) id 1q0m8c-0002iB-2y for ecs-isp@2rosenthals.com; Sun, 21 May 2023 12:42:31 -0400 Received: from mta-201b.earthlink-vadesecure.net ([51.81.229.181]:49737 helo=mta-201a.earthlink-vadesecure.net) by mail2.2rosenthals.com with esmtps (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1q0m8T-0004j0-34 for ecs-isp@2rosenthals.com; Sun, 21 May 2023 12:42:22 -0400 DKIM-Signature: v=1; a=rsa-sha256; bh=oznmOdUs+wATQIgWASS3m+WzTFHpSgywL49Y4P uO844=; c=relaxed/relaxed; d=earthlink.net; h=from:reply-to:subject: date:to:cc:resent-date:resent-from:resent-to:resent-cc:in-reply-to: references:list-id:list-help:list-unsubscribe:list-subscribe:list-post: list-owner:list-archive; q=dns/txt; s=dk12062016; t=1684687340; x=1685292140; b=GzDbsjW8lJpl+w/ConiuCprmcCJUu1GW27de5oURACTO+Sb31DPGa+w aD2Ok96gOlYH8A+fCIUsMTg4ZGUXJlsbePIVAIUfVJAjNbUxRMgMMYa+qpzftVs+2ahGEPz 7Rjj7eRLOAzc3LqGhNEJ9EuZw8GYAnxLPJ4E3EWpLebyJKHLptpDraHFb4Zhh8+RwEpBSgj lAmum3aE8VgMWTI0jmSkvO/ygDfiqvE6ypxan7raWJ6pvu4UuJ0nyKTtkJuYv5FpyCN6DEe FKJzuNT7Gt4CjRwqNYpOSLDJrcaz3uCiRlnwhubIcwXj7ReQv/7I6x9YOIEdgTC5eEr5jDU 2Ww== Received: from slamain ([108.193.252.151]) by vsel2nmtao01p.internal.vadesecure.com with ngmta id 9a071033-17613635b0ebf45b; Sun, 21 May 2023 16:42:20 +0000 Message-ID: <646a4353.12.mr2ice.fgrirsq@earthlink.net> Date: Sun, 21 May 2023 09:14:11 -0700 To: ecs-isp@2rosenthals.com Subject: Odd dig behavior X-Mailer: MR/2 Internet Cruiser Edition for OS/2 v3.00.11.24/60 Hi all, As some of you know, Peter Moylan is working on DNS issues with his pmoylan.org domain. While doing some testing with dig, I ran into some unexpected behaviors which I would like others to double check. Currently, I have DiG 9.11.28 installed. [d:\tmp]dig +nssearch pmoylan.org reports couldn't get address for 'ns1.wiz.net.au': failure couldn't get address for 'ns2.wiz.net.au': failure D:\usr2\bin\dig.exe: couldn't get address for 'ns1.wiz.net.au': no more Do any of you get differing responses? This command returns expected results on OpenSuse and lists the SOA records. [d:\tmp]dig +short pmoylan.org returns nothing which is expected given the issues Peter is working on. However, for bind 9.11.36 and 9.11.37, this command hangs. It can be killed with top's forced kill (Ctrl-F), but not a normal kill (Ctrl-K). Do any of you get differing results. dig.exe from bind 9.12.4 seems work the same as 9.11.28 for these tests. Thanks, Steven -- ---------------------------------------------------------------------- "Steven Levine" Warp/DIY/BlueLion etc. www.scoug.com www.arcanoae.com www.warpcave.com ----------------------------------------------------------------------