is this a local dns-thing?

[royalelephant]

Does anyone know what is causing my browser-site trouble?

I can trace/ping my site www.blah-blah.com from any traceroute server without any trouble, but can't get it on my browser. My host has no service problems, but my dsl-isp can't trace/ping my site. Is it my isp's dns? It seems "localized" and I don't know the terminology enough to complain vociferiously. It is causing me a little grief and would like to know how to clear it up.

grrrrr....

[Trunk Monkey]

You might have had your system "modified" by some trojan or something. I had this happen to me once...and it was Google that I couldn't get to.....but could still ping it from a command line...then it happened to another site. It was weird. Must be a newer hack.

My solution?....short of wiping my PC and starting clean?...or digging into the registry after anti-virus and scanning software turned up nothing?

EDIT the "HOSTS" file.
The local HOSTS file takes precedence over any local/remote DNS settings or redirects that are in place.

Go to your HOSTS file and make an entry with the IP address and domain name of the websites in question.
Follow the syntax thay give you as an example in the HOSTS file itself...follow that.
(the # sign should be removed)

In XP it will be here:
C:\Windows\system32\drivers\etc

Just search you windows directory for it and open it with NOTEPAD.

Realize...this is just a band-aid...your machine likely has been hijacked in some way and you need to find the true cause of the problem. I got fed up with it and formatted my machine eventually. It took less time than searching for it.

-good luck

[jk3210]

FWIW, I had a similar problem last year that lasted 4 months. I couldn't get to my site AT ALL, but everyone else could. Trace-RTs timed-out on me.

The problem turned out to be that my [large] DSL-ISP had instituted some obscure security thing that was conflicting with my web host, and only from a certain section of my state.

The problem got resolved shortly after I did a whois on my ISP and called the Director of Network Architecture (probably a coincidence, but I can dream, can't I).

[royalelephant]

Thanks Trunk Monkey, but could it be "me" when the support guys at my dsl's ISP can't raise my site with a ping either? Could the trojan/f*ckup be on their server/dns?

[added]
One more "clue"
All 3 PC/laptops on our home network cannot raise the site via our DSL via Company A's ISP but we can get to the site fine when we switch over to our backup dial-up at run by Company B.

[royalelephant]

AH... the problem was resolved but one of my IP's techs emailed me this line...

"The IP has been banned in the past for various SPAM and phishing scams and that may also be part of the problem."

My heart missed a beat... my site was until recently well-liked by Google but has dropped off the map, so to speak... I am white hat all the way and don't use any oddities... strictly content and updating... but I got whacked hard... might the problem be my webhost? Under these circumstance should I get ready to move everything to a webhost with a clean rep?