[110] in Hesiod
hesiod nameserver limitations
daemon@ATHENA.MIT.EDU (Mark Rosenstein)
Mon Nov 16 18:26:37 1992
Date: Mon, 16 Nov 92 18:20:47 -0500
From: Mark Rosenstein <mar@MIT.EDU>
To: greg@duke.cs.unlv.edu
Cc: hesiod@Athena.MIT.EDU
In-Reply-To: Greg Wohletz's message of Thu, 05 Nov 92 22:47:30 -0800 <9211060649.AA07698@Athena.MIT.EDU>
Date: Thu, 05 Nov 92 22:47:30 -0800
From: Greg Wohletz <greg@duke.cs.unlv.edu>
I recently ran into a strange problem when a group entry went beyond a
certain length (it was < 256 chars, but > 127). I thought the limit
on TXT records was 256 characters. Am I mistaken, or perhaps are
there signed chars in the nameserver or resolver code where there
shouldn't be effectively reducing the limit to 127? Or is something
else going on? The symptoms were garbled packets (apparently) being
returned whenever the record for that group was queried.
We successfully send TXT records with about 450 bytes here at MIT. If
you read the spec, it says that a TXT record is a series of one or
more of a length byte followed by that many data bytes. The code we
ship uses these unsigned bytes to put the first 255 bytes of data in
the first string, and more data in successive strings. This compiles
and runs correctly on the VAX, which has signed characters, so I'm
pretty sure we got that part of the code right.
-Mark
