TCP Receive Error

[Mark Andrews]

> Chris wrote:
> > I posted a similar message last night to the newsgroup, however, the error 
> > has changed somewhat.  Now I'm seeing this in my syslog:
> > Aug  1 20:36:13 localhost named[3700]: dispatch 0x82cf348: shutting down du
> e 
> > to TCP receive error: 67.19.238.254#53: connection reset
> > 
> > Its always the same IP address whereas yesterday the IP was blank <unknown 
> > address, family 48830>.  Since it works fine other times I assume its just 
> > this one IP that is a problem. Should I just ignore it?
> 
> On my caching nameserver I have been seeing these since July 31:
> 
> Aug  2 09:41:14 tesla named[18013]: dispatch 0x8face08: shutting down due
> to TCP receive error: 68.178.211.201#53: connection reset
> 
> The IP is always as above or 64.202.165.202
> 
> Fedora Core 5
> bind-9.3.2-20.FC5
> caching-nameserver-7.3-5.FC5
> 
> Mark

	It's just stupid nameservers not following RFC 1035 that
	accept TCP connections after returning "TC" to the UDP
	request then they reply to the TCP/DNS query with a TCP
	RESET.  If they don't want to answer the query then return
	a refused, or perform a graceful TCP shutdown.  The TCP
	RESET is just plain rude.

--
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: Mark_Andrews at isc.org