Slowing down bind answers ?

[Sten Carlsen]

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 here is that noone can say they were not warned.

You might offer help to reconfigure to the people.


On 05/01/14 15:13, Phil Mayers wrote:
> 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
> recursive resolvers, do them on "portable" IPs, not IPs from the subnet
> they live on, and direct the DNS traffic to them with static /32 or /128
> routes. You'll be glad you did later.
> 
>> instructions on how to reconfigure.  If you have the ownership data,
> 
> If you don't, you've got big(ish) problems ;o)
> _______________________________________________
> Please visit https://lists.isc.org/mailman/listinfo/bind-users to
> unsubscribe from this list
> 
> bind-users mailing list
> bind-users at lists.isc.org
> https://lists.isc.org/mailman/listinfo/bind-users

-- 
Best regards

Sten Carlsen

No improvements come from shouting:

       "MALE BOVINE MANURE!!!"