Random Dns error!

[Adam (Snowboard)]

I did some more testing today and the problem does seem to be within the
dns. I tried connecting to www.snowboard.com through telnet via port 80
and could not connect. The connection was refused for some reason. So now I
guess the problem is beyond dns as it resloves the ip of the website
(64.114.6.30) but refuses to connect to the server. So the error is more of
a connection error. Does anybody know where I can get some info concerning
this type of error? Has anybody else encountered this before? I will upgrade
to bind 8.2.5 and see if this fixes the problem. I tried doing a tracert on
our name server and it doesn't seem to be slow.

----- Original Message -----
From: "Danny Mayer" <mayer at gis.net>
To: "Adam (Snowboard)" <adam at snowboard.com>; <bind-users at isc.org>
Sent: Thursday, November 29, 2001 7:32 PM
Subject: Re: Random Dns error!


>
> At 02:45 PM 11/29/01, Adam (Snowboard) wrote:
> >I am receiving a DNS error on one of my big websites (snowboard.com). The
> >error does not happen all the time. It seems to happen randomly
throughout
> >the day. It ussually happens in groups and takes about two to three
> >minutes to clear up.
> >
> >Here is a typical scenario:
> >1) I open my web browser to snowboard.com
> >2) The browser resolves the ip address correctly to 64.114.6.30
> >3) The browser tries to connect to the 64.114.6.30 and receives a dns
error.
> >4) I try pinging the ip 64.114.6.30 and www.snowboard.com and they both
work
> >5) I connect to another website that we serve and it works
> >6) I refresh the browser and get a few more dns erros, and then finally
it
> >works again.
> >
> >NOTE: This only happens on the website snowboard.com. I have never seen
> >this error before on any other websites we serve.
> >
> >We are running BIND 8.2.4 on a winnt 4.00.1381. And our webserver is
winnt
> >4.00.1381 with iis 4.0. If anyone one else has ever come across a similar
> >problem I would like to hear about it. If anyone has any ideas as to what
> >kinds of things I can look at please let me know.
>
> Please upgrade to BIND 8.2.5 as there were a lot of NT-specific bugs fixed
> in that release. This does not answer your problem which is more to do
with
> the network and other nameservers.  Note that the query works after the
first
> time because your nameserver has received a response from snowboard.com's
> nameserver and cached the answer, or is the local nameserver the
authorative
> nameserver for snowboard.com.
>
> Have you  tried doing a traceroute to the nameserver that is authorative
for
> snowboard?  Is it slow?
>
>          Danny
>
>
>