Could it be that Yahoo saw the domain registrar change as a change in ownership, and penalized the site?
Has anyone else experienced anything like this?
Other variables might include the speed of bot fetching changing (more or less hops to your site, faster/slower DNS serving, etc), any form of bot throttling, proximity issues (relation to other GoDaddy sites on same server or IP range), mere reassessment of the site based upon the WhoIs update, change of hosting server (same website / different server set up, which may effect bot visits), down time (access issues) during the DNS update that either caused a shift or a reassessment, the use of the DOMAINCONTROL.com servers for uses other than simply hosting which may be weighted somewhere in their algo or filters, etc..
I slept on it and revisted my own post. The number of nuances and variables that may be connected to the DNS change alone that might trigger some outcome is . . mind boggling?
[edited by: Webwork at 6:20 pm (utc) on Jan. 13, 2008]