Closed fabled closed 3 years ago
The printer's pdl
line is 457 characters or so. Perhaps triggering the TXT record's 256 character "segment" limit.
The printer's
pdl
line is 457 characters or so. Perhaps triggering the TXT record's 256 character "segment" limit.
Can confirm this to be the issue, adding ugly hack to rewriting pdl to something shorter made the request go through.
Very impressive PDL list!
Yes, I confirm this issue. Very long TXT records may be split into multiple records with the same name. I will do it. RFC 4408 requires clients to concatenate these multiple records without spaces, but I bet there are broken implementations, so I'll split by commas with fallback to split in arbitrary places, if fragments between commas are too large. It will take a bit of time to implement.
It appeared to be not so simple to fix.
Unlike regular DNS, DNS-SD implies hard limit of 255 characters for each key=value pair in the TXT record (regular DNS allows to put multiple entries with the same key and split the value between them, DNS-SD explicitly disables multiple entries with the same key).
For now, I truncate PDL at the latest comma, that fits the limit, in a hope that firmware is smart enough to put common formats first, exotic formats last. If we'll see a printer that breaks this assumption, I will have to filter PDL list against a dictionary of "known" PDLs, which I really don't want to do: there is a risk that I'll forget to put something essential into this list.
Unable to publish AVAHI records for HP Color LaserJet Pro MFP M479fdn: