It is routing from the nameservers.. I would be happy to provide vb.org with secondary DNS on one of my nameserver boxes to provent this from the future. This is a prime example why you don't keep your eggs in one basket. For us we have three nameserver boxes on three different backbones, UUNet, Savvis and Internap. If their is a routing issue on one of the three, you still have the other two to handle DNS functions.
Doing a whois lookup on vb.com and vb.org show totally different name servers proving it is indeed a routing issue as everyone can reach vb.com One final note, When you are not surfing this site, go into your browser config and turn your proxy off. Proxies are a lot slower then your normal Internet connection over TCP/IP. If anyone has any questions on DNS routing, feel free to PM me
|