abbytreasures said:
The odd thing is is that I could access it no problem on my other computer
(and my friends have no problem accessing the site). So it still seems to me
that it has *something* to do with my computer .. just can't figure out what
Use ipconfig on your other computer to find out what DNS addresses
it is using. Most likely they are different. What you could do temporarily
if you wanted to is hardcode those DNS addresses in your Network
settings (instead of the getting them dynamically as you probably do
now).
You could also use nslookup to do the job that your ISP's DNS
apparently isn't doing. Hint: use its set type=any subcommand
and then if you can at least find another site's domain address
and its nameserver address(es) you can then use nslookup's
server subcommand to see if that domain's nameserver
knows the address of the site you are really interested in.
I have often wondered if that sort of manual discovery might
not be noticed by the user's real DNS, thus in a sense
training it! If not you can always substitute a correct entry
in your HOSTS file to make up for deficiencies in your
current DNS. You were lucky that you didn't need to do it
with that site you accessed by its IP address. E.g. lots of site's
hardcode their site name in the HTML for their page's components.
Without an actual HOSTS entry to override the lookup you would
be right back with the same problem, except this time the symptom
might only be Red-X in place of graphics files with unresolvable
symbolic addresses.
If you would like to explore either option but aren't quite sure
what I'm hinting at give us the DNS addresses that you are
being given and a site name that you think they aren't resolving
properly for you.
HTH
Robert Aldwinckle
---
