NS_RESP TCP Truncated Errorr

Mark.Andrews at nominum.com Mark.Andrews at nominum.com
Tue Feb 13 21:59:13 UTC 2001


	You got an answer that was too large to fit into a DNS/TCP
	answer, i.e. it was bigger than 64k or the nameserver had
	a small TCP send buffer.

	The usual cause is a web host provider that doesn't know
	what they are doing by adding PTR records for all the virtual
	sites hosted on one IP address.

	Mark

> 
> Just a short while ago, our three secondary DNS servers got hit with the
> following error appearing below.  I've searched the archives and found some
> info but not as specific as I would like.  If anyone can provide further
> specifics such as cause, etc I would greatly appreciate it.
> 
> Thanks,
> 
> Bill Smith
> <mailto:bill.smith at jhuapl.edu> 
> The Johns Hopkins University                    Washington DC: 240-228-5523
> Applied Physics Laboratory                      MD: 443-778-5523
> 11100 Johns Hopkins Road                        Fax: 443-778-5727
> Laurel, MD 20723-6099                           Web:
> <http://www.jhuapl.edu/>  
> 
> 
> 
> Feb 13 08:20:24 dnsserver.domain.edu named[22916]: ns_resp: TCP truncated:
> "36.115.254.207.in-addr.arpa" IN PTR from [207.254.115.3].53
> 
--
Mark Andrews, Nominum Inc.
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: Mark.Andrews at nominum.com


More information about the bind-users mailing list