there is a [different case from 2001](https://groups.google.com/g/comp.protocols.dns.bind/c/pIVLil7p8wA/m/Y0bxMyn5bI0J), where a (windows-based?) client sent TYPE & CLASS as little-endian, not big-endian, giving "TYPE256 CLASS256" query.

there is a [different case from 2001](https://groups.google.com/g/comp.protocols.dns.bind/c/pIVLil7p8wA/m/Y0bxMyn5bI0J), where a (windows-based?) client sent TYPE & CLASS as little-endian, not big-endian, resulting in `TYPE256 CLASS256` query.

`udp port 53 and dns.query.class > 1`?

`udp port 53 and dns.query.class > 1`

i want to generate those wrong Questions on-demand, to observe and quote the various DNS servers' log lines about them.
As well as putting all kind of TYPEs in the Q and see what they get intepreted as [https://www.netmeister.org/blog/dns-rrs.html].

i want to generate those wrong Questions on-demand, to observe and quote the various DNS servers' log lines about them, as well as to put [all kind of TYPEs](https://www.netmeister.org/blog/dns-rrs.html) in the Q and see what they get intepreted as.

"perhaps" is because, as we see below, the app sometimes didn't receive response data. unbound logs clear messages:

"perhaps" is because, as we see below, the program sometimes doesn't receive response data. unbound logs clear messages:

i hope someone out there come across this & figure out whatever is happening with the clients sending these queries.

CoreDNS, NLnet NSD doesn't log anything about these at all.

CoreDNS, NLnet NSD, systemd-resolved doesn't log anything about these at all in my testing.

i hope someone out there come across this & figure out whatever is happening with the clients sending these queries.