I hope Sergio had a good break, as did most of our BIND servers.
No segfaults during the Christmas break (25 Dec to 2 Jan), but this morning (first day back at work for most people) 2 servers running the original unpatched version (9.16.1-0ubuntu2.11) each had a segfault.
Still no similar problems on machines running the patched version (9.16.1-0ubuntu2.12~ppa1), nor on the public BIND servers which are authoritative for our own domains and are still running the unpatched version.
So if there is a possible trigger for the problem it looks to be either related to the amount of requests from client machines, or something that those client machines (mostly Windows) are putting in their requests which the servers and network hardware which stayed running over the break do not (or maybe both together).
It might be interesting to hear from anyone who has this problem on a server where there are no client machines running Windows using it.
I hope Sergio had a good break, as did most of our BIND servers.
No segfaults during the Christmas break (25 Dec to 2 Jan), but this morning (first day back at work for most people) 2 servers running the original unpatched version (9.16.1- 0ubuntu2. 11) each had a segfault.
Still no similar problems on machines running the patched version (9.16.1- 0ubuntu2. 12~ppa1) , nor on the public BIND servers which are authoritative for our own domains and are still running the unpatched version.
So if there is a possible trigger for the problem it looks to be either related to the amount of requests from client machines, or something that those client machines (mostly Windows) are putting in their requests which the servers and network hardware which stayed running over the break do not (or maybe both together).
It might be interesting to hear from anyone who has this problem on a server where there are no client machines running Windows using it.