The ironies of the Network Solutions reponse to DNFR
January 28th, 2008 by Jay DaleyYou may have seen already our post on Domain Name Front Running (DNFR) since when things have got much more interesting.
Our original post explained our position that we have seen no evidence of DNFR and regard it as an inevitable consequence of a global market. Network Solutions actually commented on that post saying they thought it did exist and needed to be tackled urgently as consumer confidence was being eroded.
Their response, which you probably have heard about, was to change their domain lookup tools so that any non-existent domain looked up through their site was automatically locked by them for four days so that nobody else could register it. You as the customer who found it could register it, but only through Network Solutions and they are clear they will not be monetising the domain before then.
So, if you have not spotted it, they appear to be front running to protect end users from front running.
The second irony is slightly more oblique. .com suffers dreadfully from the actions of domain tasters, who register huge volumes of domains and then cancel them before the grace period. The mechanisms for deciding what domains to process in this way are largely algorithmic - how long was it registered for, when was it cancelled, how many clicks did it get in the tasting period.
Once a domain has entered the domain tasting merry-go-round it can be difficult for it to get off. As soon as one taster lets it go another one picks it up because it meets the criteria for automatic registration.
So there is a possibility that the Network Solutions action could lead to a domain being picked up by tasters once Network Solutions drop the domain. In that case the consumer who wanted it but decided they did not want to get it from Network Solutions would effectively lose it forever as it would now be on the taster radar.


