Regarding change #3645 "[protocol] Use case sensitive compression when responding to queries. [RT #34737]"

Karl Auer kauer at
Thu Jan 8 10:47:05 UTC 2015

On Thu, 2015-01-08 at 11:30 +0100, Bjørn Mork wrote:
> FYI: I just got a report about some TV set-top boxes having problems as
> a result of this change.  The report included a packet dump showing a
> "working" DNS reply (matching case in query/answer, with compression)
> and a "non-working" reply (different casing in query and answer, no
> compression).

No dumps, but here is one of my (somewhat vicarious) experiences of
case-related issues; dunno if it's helpful. I don't think compression
was an issue:

Regards, K.

Karl Auer (kauer at

GPG fingerprint: 3C41 82BE A9E7 99A1 B931 5AE7 7638 0147 2C3C 2AC4
Old fingerprint: EC67 61E2 C2F6 EB55 884B E129 072B 0AF0 72AA 9882

More information about the bind-workers mailing list