Interesting new dns failures

Hash: SHA1

Sure work on an expedited removal process inside a real procedure from
ICANN down to the registry. Work on a metric and monetary system used to
punish/disincent registrys from allowing their systems to be abused. Work
on a service/solution for the end-user/enterprise that allows them to take
action based on solid intelligence in a timely fashion with tracking on
the bits of that intelligence.

three options, go play :slight_smile:

Good dialogue.

Fow what it's worth, I never advocated pushing "mechanisms" into
the DNS core to deal with this issue -- in fact, I agree with you:
It's an issue that can dealt with locally in recursive DNS, and it
also needs to be dealt with in the policies that exists.

One technical, one non-technical. Even up. :slight_smile:

- - ferg