 |  |
The DNS is running on a G3 upgraded 6100, on our ISDN line.
Re: DNS - site not visible everywhere
From: Rick Osgood
Date: Thursday, September 7, 2000
Time: 9:53:31 am
Everything worked fine until the middle of last week.
The only common thread that I find, in the few people who found this
problem, is that the error seems to be coming from a particular IP#..
144.232.213.222
That number does not appear to be one used by our ISP, and certainly
is not one of ours.
Regards,
Rick Osgood
Editor, CYBERDARTS "The Darts Zine" http://www.cyberdarts.com
E-mail: editor@cyberdarts.com
10236 Westheimer Road, Houston, Texas USA 77042-3135
713-952-5900 - fax: 425-790-6473
---------------------------------------------------------------------
---------
>At 1:17 AM -0700 9/7/00, Aaron Lynch wrote:
>>Your honor: on 9/6/00 10:43 PM, David Ross at d_ross@bellsouth.net
>>confessed:
>>
>>> Most of the large and / or broad band ISP. Bellsouth, AOL, etc... use
>>> caching servers to intercept all port 80 traffic and try and serve it
>>> locally. To do this they also have to play games with the DNS requests.
>>> I'm on Bellsouth and when they have problems, yes, surfing gets
>>>plain weird.
>>>
>>Yes, but...
>>
>>It seems to have started last week and I noticed it at home on @home. But
>>then it happened at our NOC on our T1 which is straight to savvis.
>>Then it happened at a school I administer on a frac. t1 to Verio.
>>
>>I have been having big problems with Akamai sites (ie everybody) for a
>>while, where images are not completely loading in netscape. But this is
>>different, this is like the site doesn't even exist til I hit reload. And
>>it's happened on PC's as well as my Macs, so now I'm wondering if I'm just
>>crazy :)
>
>Sounds like a DNS timeout issue.
>
>A typical TCP/IP stack will only wait about 7.5 seconds for the
>resolver to return a result. But the delay may be longer, since the
>resolver has to contact several other servers, with a potential for
>up to 15 seconds of delay before some other server responds.
>
>The net result is, your client machine's OS gives up before the
>local resolver finds the answer, but the answer, when it is
>discovered (often shortly thereafter), is cached. Thus, on reload,
>the answer comes back immediately.
>
>The solution is one of optimization - make sure you have enough
>available bandwidth, make sure the DNS server machine is fast enough
>for whatever programs it's running, etc.
>
>Keep in mind that, for Windows and Mac OS, the only resolver that
>matters is the one listed first in the TCP/IP settings. The others
>aren't used unless and until the first fails to return quickly
>enough.
>____________________________________________________________________
>Chris Buxton Men & Mice
>cbuxton@menandmice.com We Make DNS Easy!
Messages In This Thread:
Return to Digital Point Solutions' Home Page
| home | |
| products | |
| services | |
| support | |
| email lists |
| optigold isp | |
| optigold isp news | |
| home inspection | |
| inspectrix | |
| java companion | |
| oracle | |
| quickdns pro | |
| search engine | |
| veterinary |
| tips | |
| employees | |
| free tools | |
| portfolio | |
| jobs | |
| contact |
888/4-DPOINTSupport:
858/452-3696