no matching view in class 'CLASS256'

[Kevin Darcy]

No, this has nothing to do with *network* "classes", i.e. subnet masks, etc.

The clients are setting the "class" of their query to 256 instead of to 1,
which would designate the "Internet" class. DNS supports the concept of
multiple classes, or namespaces. There is no class 256 defined in the
standards. The only other defined classes are 3 ("CHAOS"), 4 ("Hesiod") and
the 255 ("any" aka wildcard) pseudo-class. Therefore the clients are "broken".
They are asking unanswerable questions, like "how was your vacation on Mars?"


-Kevin

Matthew.Touw at seagate.com wrote:

> Hi everyone,
>
> I just upgrade my server from 8.2.2-p5 to 9.1.1rc3 on a solaris 8 OS, all
> runs fine but I have the following messages on my syslog.
>
> Anyone can help to interpret what it is and how to resolve it.
>
> dns1 named[238] : client 10.4.170.60#137:no matching view in class
> 'CLASS256'
> dns1 named[238] : client 10.4.170.246#137:no matching view in class
> 'CLASS256'
> dns1 named[238] : client 10.4.170.270#137:no matching view in class
> 'CLASS256'
> ...and so on.
>
> Is it something to do with classless domain, I ran quite a number of
> segments making of different size of classes of IPs and my dns is multple
> interfaces to these segments to get fastest response, and it mentioned port
> 137 (netbios name services) which puzzled me.
>
> I read from the archive mail list that it was something to do with broken
> clients. But how do I verify and fixed this clients? What is deemed as
> broken clients.
>
> Anyone could provide some further clue on this.
>
> Thanks.
>
> :o) Matt