Novell Client does not understand DNS truncated packet from bind 9.1.2

Mark_Andrews at Mark_Andrews at
Wed Jun 12 01:33:14 UTC 2002

> miguel.paramio at wrote:
> > Novell client does not understand the way dns truncates packets in tcp
> > mode, therefore, the Novell client does not connect to the server.
> >
> > In RFC 1035 is not clear enough in the way dns should truncate any
> > packet in tcp mode. Does anybody know the way to configure dns so it
> > can truncate in different ways ?.
> TCP is stream-based, not datagram-based, so "truncation" doesn't apply. A
> TCP connection can of course be broken, due to network or system
> problems, but that's not the same as "truncation"...
> - Kevin

	Well you can get a truncated TCP response.  It's one that doesn't
	fit in 64k.  There have been a number of proposal on how to deal
	with this.  The only only that works at the moment is to request
	a AXFR and extract the oversized RRset from the AXFR.

	Also some servers use a smaller buffer to construct the TCP response
	so will truncate before 64k (old named fall into this category).

Mark Andrews, Internet Software Consortium
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: Mark.Andrews at

More information about the bind-users mailing list