|
|
 |  |
Netscape cannot promptly find some sitesFrom: Jerry Tangren Date: Wednesday, April 5, 2000
Time: 1:35:41 pmI 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 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).
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?
--Jerry <tangren@wsu.edu>
|

Return to Digital Point Solutions' Home Page |