Banned from my own server?

Sorry, but this might not make sence. But, for some reason, a couple hours ago, I tried to go t my site, but it wasnt loading. All other sites were working, so I restarted my server (mind you, the server is not in me house, its in texas). I still could not connect too the server or any sites on it. I asked other people too try connecting, and they could/can connect just fine. Its VERY irritating. I can connect too it fine if I use a proxy, but I dont want to have to use a proxy all the time. Its as if someone banned my IP from accessing the server. Any ideas?

Your ISP's DNS server's probably have a cache from when the site was down. It will probably fix itself, or you could call up your ISP and deal with tech support for an hour while they try to tell you it's not their problem.

Either way the problem is with your ISP

But why can I access other sites, but not sites on my server?

ATNO/TW is saying that your ISP is pointing http://www.yourdomain.com to a different server (instead of your server), and that it will eventually fix itself.

But my ISP doesnt even know I own the to domain name, much less, know I own the server. The website isnt even being hosted by my ISP. So how would they have access to it, if that is the case, which Iam pretty sure its not.

OK, what do you mean "wasn't loading"? 404 error? 500? 503?
From a command line;
telnet your_domain 80
HEAD / HTTP/1.0
<two enter keys>
What do you see?
Also, run dig or nslookup on your host.domain;
dig http://www. or
nslookup http://www.

Respond with the results.

What is the domain anyway?

It's entirely possible that your ISP's DNS is munged, not in that they singled out your site, though new requests and previously cached requests could be fubar. A local DNS resolver will cache (for the TTL, by the RFC) resolvable host.domains and become for the period of the TTL, a non-authoritative answerer... answerer? Sheesh.
This is the condition for which ATNO spoke, at least I think so.

Cheers.

Lol. The site wasnt loading up AT ALL. I cant telnet into anysite at all, its denying TOTAL access from my IP.

OK so that doesn't answer any of my questions. What is the URL? What do you see when you do any of what I asked for previously?

Hard to help, with two hands tied behind my back.

Cheers.

http://www.stolenkingdoms.net
You can access it fine, I cannot. The server is blocking my IP, or thats what it appears like. When I do what you asked me, I just get timed out.

Have you tried running a traceroute and see where it stops. Also, if this is a linux box you should by no means be using telnet. Run a trace route though and see where it gets stopped, that will make it easier to find the answer.

Correct. This is exactly what I was refering to. And I suspect if he tries ping or tracert it will stop on the first hop which means his ISP is still the problem.

Rat, to make the tech lingo a little more understandable, the ISP's DNS servers will cache frequently requested sites so they are not constantly having to do name resolution lookups. If they happened to cache your site when it was down, then they will return an error since they are trying to resolve your site from their cache. The resolver cache will clear itself in a specified time period. This can vary depending on the timeout set by your ISP. They will need to either flush their DNS cache or you can call them and scream at them to do it. One other thing you can try is Start | Run and type: ipconfig /flushdns, since it is possible that the bad cache is on your own machine.

OK, here is what I was talking about.
If I run dig, here's what I get;


If I run a telnet (yes, you can telnet all day long to the host or IP, as long as you specify the port -- it helps t/s issues as it returns host header information);



Alternatively, you can run nslookup (instead of dig) to see what IP is being provided by your resolver;


Non-authoritative in this case, shows that since I recently did a lookup, my DNS resolver has cached the previously requested information.

It should not vary by ISP, rather they should respect the TTL's (Time To Live) set by the authoritative DNS and when that timeout occurs, refresh the data. I say *should* because there are many which do not, especially if the value is too low. RFC-1035 states this value as minimum, though the de-facto standard is to use it as default.

It is possible that someone may have set your IP, or IP range as a 'deny' rule in the httpd.conf, though unless a DoS originated from that block, it seems unlikely.

To test the DNS problem theory, you could always connect in a browser to the IP, 216.127.70.130.
As in, http://216.127.70.130/

If that works, you have DNS issues, if it still does not work there could be routing issues. As previously stated, a traceroute (*nix) or tracert (Winders) will show you where you stop the hop.
Posting that, will help as well.
Out of curiosity, where are you located? I have access to a service called Keynote, which provides me with access points all over the place -- hundreds upon hundreds all over the globe -- to test this sort of issue from various backbones. It's possible I have an access point someplace close to you which might use the same routing -- outside of your ISP's network that is.
Cheers.

Wow! That's pretty darn slick Daemonguy.

Cheers for that!

No worries. I have my moments, few and far between as they are.
Cheers.