gaijintech.com ... almost online!

[McNevin]

A name server would start its search for an IP address by contacting one of the root name servers. The root servers know the IP address for all of the name servers that handle the top-level domains. Your name server would ask the root for www.howstuffworks.com, and the root would say (assuming no caching), "I don't know the IP address for www.howstuffworks.com, but here's the IP address for the COM name server."

The root server knows the IP addresses of the name servers handling the several hundred top-level domains. It returns to your name server the IP address for a name server for the COM domain. Your name server then sends a query to the COM name server asking it if it knows the IP address for www.howstuffworks.com. The name server for the COM domain knows the IP addresses for the name servers handling the HOWSTUFFWORKS.COM domain, so it returns those. Your name server then contacts the name server for HOWSTUFFWORKS.COM and asks if it knows the IP address for www.howstuffworks.com. It does, so it returns the IP address to your name server, which returns it to the browser, which can then contact the server for www.howstuffworks.com to get a Web page.

The other key is caching. Once a name server resolves a request, it caches all of the IP addresses it receives. Once it has made a request to a root server for any COM domain, it knows the IP address for a name server handling the COM domain, so it doesn't have to bug the root servers again for that information. Name servers can do this for every request, and this caching helps to keep things from bogging down.

Name servers do not cache forever, though. The caching has a component, called the Time To Live (TTL), that controls how long a server will cache a piece of information. When the server receives an IP address, it receives the TTL with it. The name server will cache the IP address for that period of time (ranging from minutes to days) and then discard it. The TTL allows changes in name servers to propagate. Not all name servers respect the TTL they receive, however. When HowStuffWorks moved its machines over to new servers, it took three weeks for the transition to propagate throughout the Web. We put a little tag that said "new server" in the upper left corner of the home page so people could tell whether they were seeing the new or the old server during the transition

[enderzero]

Any idear why I am unable to hit the website from the IP? I can get into the ftp no problem?

http://69.50.212.214

[McNevin]

Hows that whole thing going, havnt heard much from the endar lately.

[enderzero]

These jokers are not very helpful. Plus their shit is slow.

So when I switched all my domain registrations to the very cool registerfly gaijintech was automatically setup with ns3.accuwebhosting.com and ns4.accuwebhosting.com. I am guessing that registerfly just copied whatever settings were with my old registrar (dotster). The only other way they got those were by contacting accuwebhosting, right?

I switched registrars in June and gaijintech was working fine for weeks. I had just started a major phpbb project and I was actually getting some work done. Then it just went down. I changed nothing.

I emailed them and they wouldn't even give me the sites IP address until like the 6th email and then they acted like I had been given it long ago. So they eventually gave me the correct name servers ns1 & ns2.accuwebhosting.info. I put those in at registerfly on Thursday but it still isn't resolving. Come on global update! ...or am I missing something here? The worst part is that even with the IP address I can't work on the phpbb stuff because it needs to resolve to the domain.

I imagine it is completely their fault that gaijintech.com is not an incredibly successful company today.

[enderzero]

FINALLY!!

Hey accuwebhosting...