Richard Franckowiak wrote:
>>-----Original Message-----
>>Has anybody else seen this? I have a 98SE machine on a
>
> local network.
>
>>IP configuration is static, using a local unix machine
>
> for DNS.
>
>>Occasionally, network connections will hang during name
>
> lookup, for up
>
>>to 2 minutes. (May be from any network program:
>
> Netscape, IE, telnet,
>
>>etc.) During that time, any other connection attempts
>
> from this machine
>
>>that require a DNS lookup will also hang. (I.E., opening
>
> newsreader in
>
>>Netscape is hung with "resolving host" status. If I then
>
> try to ping
>
>>something by name, ping will hang as well.) Eventually,
>
> any/all hung
>
>>processes will continue all at once. There doesn't seem
>
> to be any
>
>>pattern to when this happens. Several times/day. It
>
> always unlocks and
>
>>completes successfully, but is very annoying.
>>
>>It does not appear to be a problem with the unix server
>
> doing DNS. I
>
>>can do nslookup on unix (even to the same host/domain as
>
> requested by
>
>>the 98 machine) during the hung time, and it works fine.
>
> Can also do
>
>>pings by name from routers, switches, etc that use the
>
> same box for DNS.
>
>>Does not appear to be a problem with the PC's network
>
> connection,
>
>>either. If I have a telnet session already open to
>
> somewhere else when
>
>>the failure hits, I can still pass traffic over it
>
> uninterrupted. Also,
>
>>can ping by ip address during those times as well--it
>
> only seems to
>
>>affect DNS requests.
>>
>>If I had to guess, I'd say that the name lookup
>
> functionality in '98
>
>>must be single-threaded, and that something is
>
> temporarily locking it.
>
>>Only question is, what?
>>
>>.
>>
>
> What is the command to run NSLOOKUP on Win98 SE? Yes, I
> am having a DNS issue with only 1 website. For the past
> 24 hours, the success rate is about 1% if using the name.
> If using the point code for the website, the success rate
> is 100% (therefore, web site is available). The cable
> internet company updated their network after the onset of
> this problem - no improvement noted. WWW.DNSSTUFF.COM
> gives you some good tools to query the network.
>
> ping -a 192.168.225.1 gives the host name for the point
> code that follows the -a argument. This point code is
> phony.
>
> P.S. I started this note about 1 hour ago; now the DNS is
> working 100%. Go figure.
I don't believe there is a version of nslookup in windows. I was using
it on one of my unix boxes, merely to prove to myself that the DNS
service was working correctly, and that the problem was somewhere in the
Windows box. Using ping with a name in windows will force a DNS lookup,
and the default output will also show you the resulting ip value before
it actually processes the ping packets.
I'm not sure if you have the same problem I do. Did DNS "hang" for a
long time, and then eventually succeed, or did it just fail outright?
Mine always succeeds, but every so often it will hang for up to 2
minutes first. The excessive delay between entering the ping command
and seeing the ip result, along with instant results from a concurrent
test to the same DNS server from a different box, clearly indicates some
kind of problem within the Windows98 system. Unfortunately, it looks
like nobody here knows enough about '98 internals to offer any guidance,
as there have been no replies to date.
Similar Threads
Linear Mode
