On Thu, 9 Oct 2003, Jeff Godin wrote: > I don't see this. The domain apparently continued to resolve until > ~10 days past the expiration date, at which time it started > resolving to sitefinder.
Are you saying that it continued resolving to mp3.com's website for up to 10 days after expiration? > This is inadequate technique, with or without sitefinder. So far, I > have seen nothing that indicates that fault for the domain expiring > lies with anyone other than the folks at mp3.com. Correct. I don't think anyone is saying verisign is at fault for not notifying them of the pending expiration. If sitefinder wasn't in the mix, perhaps mp3.com would have gotten a clue. > At the time that *someone* noticed and fixed the problem, sitefinder > was still operational. This would seem to support the theory that > the wildcard's removal was not the catalyst that caused anyone to > notice the problem, and therefore the wildcard's presence had no > significant role in preventing anyone from noticing the problem. The problem was "noticed and fixed" on Oct 6, over 24 hours after sitefinder was disabled on Oct 4.
