named errors

[Kevin Darcy]

Yeah, it could be 213.198.65.226, or anything in the path between you 
and that device.

But, the better question to ask is: why is this client forming a TCP 
connection in the first place? Is it one of your slave nameservers 
performing a zone transfer? Is it because you have responses that are 
larger than 512 bytes and this is triggering TCP retries because either 
a) the clients don't support EDNS0, b) something in the path is 
erroneously not passing EDNS0 or c) EDNS0 is supported end-to-end, but 
something in the network path doesn't support IP fragmentation and thus 
the EDNS0 packets aren't getting through?

                                                                         
                                                                         
             - Kevin
On 8/10/2010 10:29 AM, fddi wrote:
> hello,
>
>
> on my server I have many errors like this one:
>
> Aug 10 11:12:01 server2 named[31822]: dispatch 0x2aaaac159550: 
> shutting down due to TCP receive error: 213.198.65.226#53: connection 
> reset
>
> anyone could give me some more hint ?
> does this mean that 213.198.65.226 is broken ?
>
> thanks
>
> Rick
>
> _______________________________________________
> bind-users mailing list
> bind-users at lists.isc.org
> https://lists.isc.org/mailman/listinfo/bind-users
>
>
>