Bind stops listening on TCP port 53 port 53

[Jan Hansen]

In relation to my previous post "Bind 9.6.1: skipping zone transfer, but 
why?" and Scott Hanedas post "Zone transfer failing":

I've just discovered that my Bind 9.6.1 on windows server 2008 stops 
listening on tcp port 53 from time to time, UDP works fine. This gives 
me errors on the slave servers like this:

01-jul-2009 10:31:14.437 general: notice: running
01-jul-2009 10:31:36.265 notify: info: client 213.173.250.146#46147: 
received notify for zone '3yhta.dk'
01-jul-2009 10:31:36.265 general: info: zone 3yhta.dk/IN: Transfer started.
01-jul-2009 10:31:37.187 xfer-in: error: transfer of '3yhta.dk/IN' from 
213.173.250.146#53: failed to connect: connection refused
01-jul-2009 10:31:37.203 xfer-in: info: transfer of '3yhta.dk/IN' from 
213.173.250.146#53: Transfer completed: 0 messages, 0 records, 0 bytes, 
0.937 secs (0 bytes/sec)
01-jul-2009 10:34:31.218 notify: info: client 213.173.250.146#52882: 
received notify for zone '3yhta.dk'
01-jul-2009 10:34:31.234 general: info: zone 3yhta.dk/IN: refresh: 
skipping zone transfer as master 213.173.250.146#53 (source 0.0.0.0#0) 
is unreachable (cached)

I tried using a dig tool which would give me an answer using UPD, but 
not TCP. Restarting the ISC bind service resolved that problem.

Before the timestam of the problems, I see the following in the masters 
logfile. Could the "dispatch: error: dispatch 01ED8108" error message 
shed some light on what has caused named to stop listening on tcp?


(these two lines indicate that tcp is working)
30-jun-2009 14:57:28.830 xfer-out: info: client 213.173.250.147#2626: 
transfer of '3yhta.dk/IN': AXFR started
30-jun-2009 14:57:28.830 xfer-out: info: client 213.173.250.147#2626: 
transfer of '3yhta.dk/IN': AXFR ended
(and here we see something strange)
30-jun-2009 15:01:04.455 dispatch: error: dispatch 01ED8108: shutting 
down due to TCP receive error: <unknown address, family 48830>: network 
unreachable
30-jun-2009 15:01:04.768 edns-disabled: info: success resolving 
'NS.ICANN.ORG/A' (in 'ICANN.ORG'?) after reducing the advertised EDNS 
UDP packet size to 512 octets
30-jun-2009 15:05:46.924 dispatch: error: dispatch 01ED8108: shutting 
down due to TCP receive error: <unknown address, family 48830>: network 
unreachable
30-jun-2009 15:05:47.158 edns-disabled: info: success resolving 
'zc.akadns.org/AAAA' (in 'akadns.ORG'?) after reducing the advertised 
EDNS UDP packet size to 512 octets
30-jun-2009 15:05:47.174 edns-disabled: info: success resolving 
'zd.akadns.org/AAAA' (in 'akadns.ORG'?) after reducing the advertised 
EDNS UDP packet size to 512 octets
30-jun-2009 15:05:47.174 edns-disabled: info: success resolving 
'za.akadns.org/A' (in 'akadns.ORG'?) after reducing the advertised EDNS 
UDP packet size to 512 octets
30-jun-2009 15:05:47.190 edns-disabled: info: success resolving 
'zd.akadns.org/A' (in 'akadns.ORG'?) after reducing the advertised EDNS 
UDP packet size to 512 octets
30-jun-2009 15:05:49.799 edns-disabled: info: success resolving 
'zb.akadns.org/AAAA' (in 'akadns.ORG'?) after reducing the advertised 
EDNS UDP packet size to 512 octets

Best regards,

Jan Hansen