Server unable to resolve certain domain.

[Kevin Darcy]

BIND 9 debugging sucks wind. What domain are you having trouble resolving?

"Message class could not be determined" sounds like a malformed packet of some
kind.


- Kevin

kmcelwain at pointcloud.com wrote:

> Good afternoon,
>
> I'm using bind 9.1.2.  I'm trying to resolve a certain domain on a server.
> It seems there's problems with one domain I can not resolve, so I'm looking
> into debugging.  I've set that up and have the output, but I can't make
> head nor tails of it.  Can anyone explain the error in this output?
>
> [root at dhcp /root]# dig ns www.zap3d.net
>
> results in
>
> May 22 15:39:36.477 client 192.168.99.8#1191: UDP request
> May 22 15:39:36.477 client 192.168.99.8#1191: using view '_default'
> May 22 15:39:36.477 client 192.168.99.8#1191: request is not signed
> May 22 15:39:36.477 client 192.168.99.8#1191: recursion approved
> May 22 15:39:36.477 client 192.168.99.8#1191: query
> May 22 15:39:36.478 client 192.168.99.8#1191: ns_client_attach: ref = 1
> May 22 15:39:36.478 client 192.168.99.8#1191: query approved
> May 22 15:39:36.478 client 192.168.99.8#1191: replace
> May 22 15:39:36.478 clientmgr @0x40141a30: createclients
> May 22 15:39:36.478 clientmgr @0x40141a30: recycle
> May 22 15:39:36.478 createfetch: zap3d.net. NS
> May 22 15:39:36.478 fctx 0x40179e78: create
> May 22 15:39:36.478 fctx 0x40179e78: join
> May 22 15:39:36.478 fetch 0x4014b038 (fctx 0x40179e78): created
> May 22 15:39:36.478 fctx 0x40179e78: start
> May 22 15:39:36.478 fctx 0x40179e78: try
> May 22 15:39:36.478 fctx 0x40179e78: cancelqueries
> May 22 15:39:36.478 fctx 0x40179e78: getaddresses
> May 22 15:39:36.478 dns_adb_destroyfind on find 0x4017f4b8
> May 22 15:39:36.478 dns_adb_destroyfind on find 0x4017f4b8
> May 22 15:39:36.479 dns_adb_destroyfind on find 0x4017f4b8
> May 22 15:39:36.479 fctx 0x40179e78: no addresses
> May 22 15:39:36.479 fctx 0x40179e78: done
> May 22 15:39:36.479 fctx 0x40179e78: stopeverything
> May 22 15:39:36.479 fctx 0x40179e78: cancelqueries
> May 22 15:39:36.479 fctx 0x40179e78: sendevents
> May 22 15:39:36.479 fetch 0x4014b038 (fctx 0x40179e78): destroyfetch
> May 22 15:39:36.479 fctx 0x40179e78: shutdown
> May 22 15:39:36.479 client 192.168.99.8#1191: error
> May 22 15:39:36.479 client 192.168.99.8#1191: send
> May 22 15:39:36.479 client 192.168.99.8#1191: sendto
> May 22 15:39:36.479 client 192.168.99.8#1191: ns_client_detach: ref = 0
> May 22 15:39:36.479 client 192.168.99.8#1191: senddone
> May 22 15:39:36.479 client 192.168.99.8#1191: next
> May 22 15:39:36.479 client 192.168.99.8#1191: endrequest
> May 22 15:39:36.480 fctx 0x40179e78: doshutdown
> May 22 15:39:36.480 fctx 0x40179e78: destroy
>
> Also,  I've been getting a lot of these errors .
>
> May 22 11:54:34 dhcp /usr/local/sbin/named[607]: client 192.168.99.8#1521:
> message class could not be determined
> May 22 11:59:41 dhcp /usr/local/sbin/named[608]: client 192.168.99.8#1533:
> message class could not be determined
> May 22 12:04:49 dhcp /usr/local/sbin/named[608]: client 192.168.99.8#1546:
> message class could not be determined
>
> Thanks,
>
> Kirk McElwain
> Network Administrator
> Point Cloud, Inc.
> (763)551-1950 ext. 21