From: "Steven Levine" Received: from [192.168.100.201] (HELO mail.2rosenthals.com) by 2rosenthals.com (CommuniGate Pro SMTP 5.4.10) with ESMTP id 12684217 for ecs-isp@2rosenthals.com; Sat, 05 Apr 2025 14:34:21 -0400 Received: from [192.168.200.201] (port=58511 helo=mail2.2rosenthals.com) by mail.2rosenthals.com with esmtp (Exim 4.97.1) (envelope-from ) id 1u18LU-000000007jt-1gJB for ecs-isp@2rosenthals.com; Sat, 05 Apr 2025 14:34:20 -0400 Received: from mta-202b.earthlink-vadesecure.net ([51.81.232.241]:58421 helo=mta-202a.earthlink-vadesecure.net) by mail2.2rosenthals.com with esmtps (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.97.1) (envelope-from ) id 1u18LJ-000000000eb-0jws for ecs-isp@2rosenthals.com; Sat, 05 Apr 2025 14:34:09 -0400 DKIM-Signature: v=1; a=rsa-sha256; bh=4hfCVz0RWl9/hwAKGS1EKEy7lDt/Od2ISsFA4D QsGJM=; 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-unsubscribe-post: list-subscribe:list-post:list-owner:list-archive; q=dns/txt; s=dk12062016; t=1743878048; x=1744482848; b=RoKcsoO3VYif3Nk8UvFoI+gazpw dhDXU9BT9+/0NvMSGH+8Pruv+cqmLeej16AjHR1j11UpTixMJLG2hX9nxJWNuTzBpV9b1Fj UPM+fvj5gC53CBaVfiunM7zhrkH+S7di51FK7T98iy9PXAl9EFgk8K+ZTQnAWCimY/vwznL jhCqxNnSMLdv7zScEgEFSphFoJ9tY4Gt/kVDG+Yh6Hktc9nxJ1iRqmeLtoTsTwahVCkeE/v v8S3sVtGmsXUo7ukrULnDhyDdsb14QHOgNX2wZyXlFOPsn4PM4H+HQgoScZDcOI9Npv/NmZ 4b6X+KKOJOUvFe6SjSdky05IG4QiywQ== Received: from slamain ([172.56.177.206]) by vsel2nmtao02p.internal.vadesecure.com with ngmta id dfa0b375-18337fd8620aed82; Sat, 05 Apr 2025 18:34:08 +0000 Message-ID: <67f17548.37.mr2ice.fgrirsq@earthlink.net> Date: Sat, 05 Apr 2025 11:24:08 -0700 To: "eCS ISP Mailing List" In-Reply-To: Subject: Re: [eCS-ISP] Updating bind X-Mailer: MR/2 Internet Cruiser Edition for OS/2 v3.00.11.24/60 In , on 04/05/25 at 11:01 AM, "Massimo S." said: Hi, >i don't know what to answer OK. >if there is an issue in a zone of a domain, the excpetion will show again Perhaps. Not all zone file errors are going to cause bind to trap. >now we have the latest execptq env. surely it will give a better output The output will definitely be better. Only time will tell if the better output will make it easier to track down the reason for the exception. FWIW, when you scanned the original exceptq report, you should have noticed 0367F780 : 0367F844 0367F840 00000008 00000008 : D.g.@.g......... 0367F790 : 4367F8C0 504D2F3A 452F4E54 6E2F4354 : ..gC:/MPTN/ETC/n 0367F7A0 : 64656D61 74762F62 69706D69 69746E61 : amedb/vtimpianti 0367F7B0 : 6D6F632E 1FFC1A00 0367F838 0367F838 : .com....8.g.8.g. This is possibly the name of the zone file that triggered the exception. Steven -- ---------------------------------------------------------------------- "Steven Levine" Warp/DIY/BlueLion etc. www.scoug.com www.arcanoae.com www.warpcave.com ----------------------------------------------------------------------