(cross-post added to XP Networking)
Mikeplus4 said:
Frank,
I just entered the command you wrote below and rebooted. Still can't get to
the URLs I mentioned earlier. FYI, I tried to get to
www.wtt.com today (my
wife loves tennis) and it gave me the same error "page cannot be found". How
about deleting my cookies?
Make sure first you don't have a DNS problem with that site.
For example, the first time I tried using nslookup with that name
both my DNS servers timed out. When I retried it was found quickly.
So evidently there was sufficient delay doing the lookup the first time
that nslookup gave up. This suggests the same problem could happen
to iexplore.exe when it has to do the lookup the first time. Then what if
there is insufficient persistence in your DNS server in contrast to mine?
Then you might always see that timeout symptom.
Another surprise for me was that even when I tried ping -n 1
www.wtt.com
and that lookup worked, e.g. as evidenced by the first line of its response:
Pinging
www.wwt.com [198.200.139.195] with 32 bytes of data:
when I then immediately tried to check what information the dnscache
was retaining because of that lookup, there was none! E.g.
ipconfig /displaydns
just showed information loaded by the HOSTS file about localhost
(my only entry in that file.)
(FYI often ping -n 1 can be used in these cases to try loading some
of the DNS lookup records into the dnscache so the user's DNS servers
don't have to be reaccessed. nslookup's lookup in contrast is not retained
locally but as I showed you can increase the probability of it being retained
by your DNS servers.)
Hmm... I just tried using nslookup interactively with its set debug command
and then retried the lookup. It shows that the Time-to-live for the record
should be enough for me to see it in my dnscache.
<example>
QUESTIONS:
www.wwt.com, type = A, class = IN
ANSWERS:
->
www.wwt.com
internet address = 198.200.139.195
ttl = 462 (7 mins 42 secs)
</example>
So I don't know what this means. Perhaps there is a clock somewhere
out of whack?
I'm cross-posting these observations to the XP Networking NG
in case someone there has some better explanations for our
combined symptoms with this lookup.
HTH
Robert Aldwinckle
---