Netscape cannot promptly find some sites

Re: Netscape cannot promptly find some sites

From:

Date:

Time:

At 1:30 PM -0700 4/5/00, Jerry Tangren wrote:
>I have a variety of machines I use for web servers, all
>of which have entries in our QuickDNS based server. From
>the network here at work I get fast response time from
>all servers.
>
>When I connect from home through a dial-up ISP,
>I get good response time from some of the web servers,
>but others time-out (in the "looking for" phase). If
>I ask Netscape again for the timed-out site, it usually
>comes up promptly and continues to promptly display
>pages for the rest of the session. All is well, but
>most likely few of our clients are willing to click
>again.

The problem you describe is in DNS resolution. How are these domains
delegated? Are there any significant differences between the fast
domains and the slow domains?

>The servers that produce poor response are on a
>NetBSD system and a MkLinux system, running Apache.
>The servers that produce good response are on Macintosh OS 8
>(Filemaker) and Windows NT 4 (IIS).

Since all of their DNS records are handled by your QuickDNS Pro
server, the web server platform shouldn't affect the speed of DNS
lookups.

>The only other difference
>of which I am aware is the reverse look-up. We're
>on a Class C
>subnet provided from the main university campus.
>The reverse look-ups for the two good servers are
>the same as the server names. For the
>poorer systems, they reverse look-up default names
>first entered into the system when the network was
>established.
>
>Would updating the reverse-lookups fix the problem,
>or am I looking for specific performance hits?

It's unlikely that the reverse lookups have anything to do with this
problem, but I'm not willing to rule it out.
____________________________________________________________________
Chris Buxton cbuxton@menandmice.com
Men & Mice http://www.menandmice.com
Makers of: QuickDNS Pro

Sales:
888/4-DPOINT

Support:
858/452-3696