How Did a Forgotten Top Level Domain Delegation Push Dnsimple to Require Proof of Rights Before a Domain Comes Back Into Dnsimple?

DNSimple requires a person to prove they actually have the rights before a domain that used to be with DNSimple comes back into DNSimple. DNSimple does not make a change when ownership cannot be proved.

The speaker thinks the high profile case was a registry for one of the top level domains and cannot recall the name. The registry had something set up, stopped using it, and forgot to remove the delegations. Somebody started seeing traffic flowing through that was useful to attack in another path. A lot of things have to come together and create a perfect storm. It can be dangerous, and it happens, so DNSimple protects against it. Somebody who wants to own the domain, or is bringing it back into DNSimple, has to make a proof and show that they actually have the rights. The case is rare, and it does happen.

DNSimple had already considered a lot of the more human attacks. Really strict protocols deal with folks requesting changes to a domain when DNSimple cannot prove that they own it. DNSimple does not make the change.