As mentioned in my previous post, I am a network engineer/consultant; one of my specialties is Internet security and connectivity. I have done as much diagnostic work as I can, and the problem many of us have been having is not with the sdreefs.com server itself, but with the Domain Name System (aka DNS).
DNS is the service which translates server/domain name like www.sdreefs.com into an Internet Protocol (IP) address (sdreefs' IP address is 70.84.14.194) which is then in turn used for your ISP to route the traffic to the proper destination. The heart of the DNS system is a group of servers called root servers which are operated by various companies like Verisign and Cogent, some universities, and federal entities like NASA and the DoD.
Hosting companies like minidedicated.com (which hosts sdreefs) run DNS servers for the domain names they host. On a periodic basis (usually daily), such DNS servers execute a data transfer, which is an exchange of DNS records for the applicable domains. Ultimately, all of the root servers know which specific DNS server(s) contain the specific records for a given domain (like sdreefs.com).
When you fire up your favorite Internet browser, and type in a URL (http://www.somewhere.com), your computer sends a query to your ISP's DNS server. If your ISP's DNS server doesn't have the information already cached (stored temporarily), it sends a query to another DNS server up the line so on and so forth until it gets a response that tells it which DNS server hosts the records for somewhere.com. That DNS server, when queried, responds with a message that says "www.somewhere.com's IP adress is 55.248.24.119"; this info is sent back to your computer, and your computer then sends the request for the default web page for www.somewhere.com to 55.248.24.119.
Although this whole process may sound complex, normally this process takes place in milliseconds. Something is awry with the records for SDReefs, or the proper exchange thereof. As far as I can tell, both of the DNS servers for sdreefs.com are correct. Some ISPs are getting the right info (seems like TWC is good); some are getting it sporadically (Cox), and some don't seem to be getting it at all (like ATT, based on the reports here and other forums).
As of the last communications from Blake, he was working with the hosting company (and the DNS provider for the sdreefs.com domain) to resolve the issue. That, however, was some time ago.
As a networking professional, I know that sometimes problems like this can be a real PITA to resolve, and I can be patient. But I would like to see some sort of status update from Blake.
Reply With Quote
Originally Posted by Technoviking
If reports are good in a couple days, then take it out.
