Hi All, Please accept my apologies for asking a generic BIND/rsyslog question here, but I've searched on and off for months, now, how to solve this problem to no avail. I have a server that was writing around 300 MB a day to /var/log/messages in just these types of entries: TCP: Peer 0000:0000:0000:0000:0000:ffff:b4b5:3097:55344/80 unexpectedly shrunk window 1944967302:1944991761 (repaired) The log entries went away and /var/log/messages' size dropped to normal after named was configured to stop listening on IPv6 port 53 thus(*): - - - - - 8< - - - - - listen-on-v6 port 53 { none; - - - - - 8< - - - - - [*] if IPv6 were implemented at this data center, I'd have simply configured BIND (9.8.2) to utilize IPv6 Per, in another thread several weeks (months?) ago, you predicted this method would have unwanted side effects ... does this look like the problem you were describing? I just recently received a bounced e-mail stating (particulars obfuscated): "The mail system : connect to mx?.??????.edu[????:??:???:???::??]:25: Network is unreachable" I'm gathering the intended recipient's mail system is IPv6 only? What is the core problem here, and, how do I resolve it? Or else how do I suppress all these 'unexpectedly shrunk window' messages so the server doesn't stumble every time the logs are rotated? TIA and regards, Carl -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org