I talked to some supervisor at godaddy earlier and they said they will get back at me, if it's not jodohost's fault then I apologize but all this time until now all you guys are telling me that my sites are fine when they're not.
I think only dnsstuff has the right records because you guys use dnsstuff routinely so the records must be cached on their name servers since before the problem began. Even before I started this thread I showed the links to the other test to Tamnaya and all s/he said is "your site is fine http://dnsstuff.com/tools/lookup.ch?name=xml.rebellionmusic.com&type=A", I said "so because it's fine for dnstuff the rest doesn't matter?", then s/he said "yes", that is when I got upset.
Similarly the other morning when my site went down I now realize that Deeppak wasn't getting the same error as I was, I was getting a "Server could not be found or DNS error" and he was looking at the default page on the site (which is not used and don't have it's codebehind dll, but I wasn't even able to access that), even after I told him I was getting a server could not be found error he just kept insisting that it was a code problem without telling me that he's seeing something else, so I get upset cause as far as I know he's telling me that the "Server could not be found" is a code problem!
So the main problem here is communication cause if tells me that he's not getting the same error as I am then we would have made a lot of progress in figuring out what was wrong which I'm pretty sure now was the following:
I got an ASP.NET webservice to handle large file uploads and was working on a client application to upload the files, I had to write the upload client from scartch using socks cause it's the best way to have an accurate progress bar. I got it working on my server but your server handles http requests a bit different (since it's iis6 vs 5.1) so went I tested it on the your server the request hung during the handshake, I tried a second time and the same happens, then I checked it on the browser and I got a server could not be found since iis only allows two connections to the same host from 1 ip address and the other two where still waiting for the handshake to complete and since it needs to handle large file uploads it won't timeout in about an hour. I have taken steps to prevent that from happening again, but at the moment the service needed to be rebooted in order to kill those connections.
