<<<
Chronological Index
>>> <<<
Thread Index
>>>
Fast Flux
- To: fast-flux-initial-report@xxxxxxxxx
- Subject: Fast Flux
- From: Ben Gelbart <wehaveitall.netwebmaster@xxxxxxxxx>
- Date: Wed, 28 Jan 2009 07:48:15 -0700
Hi,
All of these NEED to be enforced:
�takedown� efforts by making it difficult to track illegal activity and
identify its actual location. .Registries and registrars can curb the
practice in two ways: (1) by monitoring DNS activity (fast flux is easy to
detect) and reporting suspicious behavior to law enforcement or other
appropriate reporting mechanism; and (2) by adopting measures that make fast
flux either harder to perform or unattractive. Some possible measures that
have been suggested include:
� authenticating contacts before permitting changes to NS records;
� preventing automated NS record changes;
� enforcing a minimum �time to live� (TTL) for name server query responses6;
� limiting the number of name servers that can be defined for a given
domain; and (I think this one might be a maybe)
This is a VERY serious problem.
I am sending this on behalf of spacequad anti-spam services.
http://www.spacequad.com/article.php/fastfluxhosting
We are all joining together to let you know that we realize this is a
serious problem.
We appreciate your understanding.
-Ben
<<<
Chronological Index
>>> <<<
Thread Index
>>>
|