On 05/01/14 21.55, Nicolas C. wrote:
>
>
> 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 :)
>
Personally I would cut off access for all tha
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 i
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.
The point
On 05/01/2014 13:25, Timothe Litt wrote:
To get people's attention, NXDOMAIN to www.* queries is often reasonably
Interesting idea; implemented how?
It may be better to simply alias (if necessary, route) the old IP
Piece of advice for anyone not already doing this; when you deploy
recursi
On 04-Jan-14 14:58, Nicolas C. wrote:
On 03/01/2014 18:00, wbr...@e1b.org wrote:
From: Mark Andrews
After that specify a final date for them to fix their machines by
after which you will send NXDOMAIN responses. Sometimes sending a
poisoned reponse is the only way to get peoples attention.
5 matches
Mail list logo
