In <list-12676175@2rosenthals.com>, on 04/01/25
    at 09:14 PM, "Massimo S." <ecs-isp@2rosenthals.com> said:

Hi massimo,

any help?

I can't help you until you help yourself and provide a proper exceptq
report.  Unfortunately for you currently I don't have time to explain yet
again, in gory detail, what a proper exceptq report means.  It's been
discussed many many times on this list and elsewhere.

DOS hint -when I receive a zipped exceptq report via private mail what was
generated by

  Exceptq Version:  7.10 (Mar  1 2011)

it's going to going at the end of the queue.  I am curious why you thought
using a 14 year old version of exceptq was a wise decision.

I am also curious why you thought it was a wise decision to send me an
exceptq report that contains lines like?

    EBP     Address    Module     Obj:Offset    Nearest Public Symbol
  --------  ---------  --------  -------------  -----------------------
  Trap  ->  1F2BDD06   LIBCN0    0001:000FDD06
  0367F084  1F2BE4D6   LIBCN0    0001:000FE4D6

Your setup is clearly missing requried xqs and/or sym files.

Common sense tells us that

  0367F354  0018E5ED   NAMED     0001:0017E5ED  lex.c#869 _isc_lex_gettoken
0001:0017E235 (lex.obj)

implies that bind is having some sort of problem parsing a token in some
data stream or file

Common sense also tells us

  0367FDD4  001F0583   NAMED     0001:001E0583  zone.c#2623
_dns_zone_cdscheck 0001:001DA98F (zone.obj)

the problem is probably in one of the zone files.

Common sense tells us that we should scan the exceptq report, bad as it
is, just in  case the name of the problematic zone file was reported.

I might be able to make some more common sense guesses with a proper
exceptq report.

Steven