On 05/01/2014 18:17, Sten Carlsen wrote:
You might also make a list of those who use the old server, send a message (assuming the management system allows identification) that the service goes down at a specific date in e.g. a month from that date. And then remove it. Threats are not much worth if the are not followed through.
And : On 05/01/2014 14:25, Timothe Litt wrote:
You can also turn on query logging (which helps slow down the old server) - and use the logs to backtrack to the machines that need to be reconfigured. Scripts can send an e-mail daily with a warning and instructions on how to reconfigure. If you have the ownership data, scripts can escalate to a manager/sponsor if ignored. Hopefully this will get you down to a manageable list of miscreants that require manual follow-up.
As I said in my original request : I did the query logging / warning but it had no effect.
I could hold them at gunpoint until they change their configuration but we have strict gun laws in France :)
_______________________________________________ Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
