1. When you re-point your domain at non-NetSol servers, they momentarily point toward a server that in turn says your A record is their "business profile" default landing page. It takes a few minutes before pointing correctly at your new name server
2. Many large caching nameservers don't obey TTL; our SOA's TTL was 7200, or 3 hours, but we saw servers at RCN, BellSouth and Cox serving our old SOA nearly 24 hours later.
Together, that means that for 24 hours, some people got this lovely page: http://www.vttcorp.com/ instead of our server.
Here's the correct recipe: a) Tell new registrar about incoming domain transfer, make him already set up nameservers. b) Set the new nameservers for your domain. c) Actually transfer the domain.
If either your old provider is nice enough to not shut down your name server as soon as he receives the transfer request (which won't benefit him in any way, because he is just helping an already leaving customer) or you follow the recipe from above, you will have zero downtime.
People using GoDaddy for both registration and DNS could find themselves in exactly the same predicament, so it makes sense that they'd want to do it carefully.
Other people have mentioned having to move Email as well, but I don't understand why people don't use Google Apps which is free and stops you from having to migrate your email all over the place when you switch hosts.
The person I replied to specified "major sites". How many major sites do you know that use GoDaddy to host their DNS?
The domains leaving are just the leading indicator. If they're going away, there's plenty of reason to believe that other customers, that will hurt them more, are working on the issue.
