spf-discuss
[Top] [All Lists]

RE: BIND TCP Failover - was Website/Wizard update for BIND Long TXT records

2005-08-10 19:39:40
-----Original Message-----
From: Leonard Mills 
[mailto:Leonard_Mills(_at_)corpnet(_dot_)sel(_dot_)sony(_dot_)com]
Sent: Wednesday, August 10, 2005 10:32 PM
To: spf-discuss(_at_)v2(_dot_)listbox(_dot_)com
Cc: Leonard_Mills(_at_)corpnet(_dot_)sel(_dot_)sony(_dot_)com
Subject: Re: [spf-discuss] Website/Wizard update for BIND Long TXT
records


Scott quoted someone who said:

message: I have run into what appears to be a BIND limitation with
long TXT records. These records are limited to 255 characters per
_line_,

That's not strictly true.  You can request that
ns3.sony.com provide you with the text record for
nothere.corpnet.sel.sony.com; the payload for that
record is 412 bytes.  Ns3.sony.com is running BIND,
more specifically named version 8.4.4.  If the
software making the request is sufficiently intelligent
to perform a query retry using TCP, you will receive
the entire record.

Querying using DiG 9.2.4, for example, will cause the
output to begin with the comment:
;; Truncated, retrying in TCP mode.

Hope this clarifies the way things work,

Len

OK, so what the submitter was experiencing wasn't a BIND limitation, but a
failure to try again with TCP when UDP didn't return the entire string?

Is that right?

Scott K