Editing Site Finder (section)

==Fallout==
A number of workarounds were developed to locally disable the effects of Site Finder on a per-network basis. Most notably, the [[Internet Systems Consortium]] announced that it had produced a version of the [[BIND]] DNS software that could be configured by [[Internet service provider]]s to filter out wildcard DNS from certain domains; this software was deployed by a number of ISPs.

On October 4, 2003, as a result of a strong letter<ref>[https://www.icann.org/resources/unthemed-pages/twomey-to-lewis-2003-10-03-en Letter from Paul Twomey to Russell Lewis 3 October 2003]</ref> from [[ICANN]], VeriSign disabled Site Finder. However, VeriSign has made public statements that suggest that they may be considering whether they will change this decision in the future. On February 27, 2004, VeriSign filed a lawsuit against ICANN, claiming that ICANN had overstepped its authority. The claim regarded not only Site Finder, but also VeriSign's much-criticised [[Wait Listing Service]]. The claim was dismissed in August 2004; parts of the lawsuit continued, and culminated in a March 1, 2006 settlement between VeriSign and ICANN which included "a new registry agreement relating to the operation of the .COM registry."<ref>[http://www.icann.org/announcements/announcement-28feb06.htm ICANN Board Approves VeriSign Settlement Agreements] ICANN, February 28, 2006</ref>

On July 9, 2004, the ICANN ''Security and Stability Advisory Committee'' (SSAC) handed down its findings after an investigation on Site Finder. It found that the service should not be deployed before ICANN and/or appropriate engineering communities were offered the opportunity to review a proposed implementation, and that [[domain name registry|domain name registries]] that provide a service to third parties should phase out wildcard records if they are used.