Site Not working?

[Gear853]

i'm not sure what's going on, but when i try to go on the site...it give me this instead (http://i6.photobucket.com/albums/y208/Gear853/animesuki.jpg)?

:(

is anyone else having this problem?

[Proto]

I don't. but the fact that Animesuki doesn't run on Apache makes me incredibly sad.

Or maybe it's just bad DNS resolution. What happens when you enter here (69.42.221.126)?

[Gear853]

that worked... weeeeird! what's going on?!

[NightWish]

I cannot tell you where that IIS7 page comes from, but I can tell you it is not from any site connected with animesuki.com, or last least any site run by those of us who run animesuki.com, I suppose one of the ad servers might use it... :eek:.

I would be curious to know what you get if you run nslookup or dig....the fact that Animesuki doesn't run on Apache makes me incredibly sad.If I may ask, why does it make you sad?

[Imperial Blaze]

Mine works just fine......

[Vexx]

sometimes an intermediate DNS cache is "poisoned" or corrupt and to blame for this sort of thing.

fun with intarwebbing...

@Lord Zetsuei: that would be useful if you included traceroute or other diagnostic information but as it is, it isn't.

[Gear853]

well i flushed my DNS Cache, and it's still doing it.

but it works when i just enter the IP address. odd, very odd.

[NightWish]

odd, very odd.Not that odd if you are suffering what Vexx describes; if a DNS cache, probably at your ISP, has been poisoned (i.e fed with false information) then it will keep passing that false information on to you each time you flush your cache and try again. Only once the cache at your ISP is flushed, or rather the invalid entry expires, and the server requests the name-to-IP mapping again, from a legitimate source, will you see a change.

When you use the IP address directly you are skipping the DNS completely and hence always get the right server. That method will stop working if we move the server to a different IP address, of course. We have no plans to do that at this time, so you're safe to use the IP until the problem with your ISP (or whatever) is resolved.

[Vexx]

There does seem to be a current problem with DNS resolving in certain parts of the world. I'm getting far more DNS lookup error results than usual today when visiting websites based in certain regions.

If I get some time I'll visit the "Storm Center" and see if anything has been reported...

[Gear853]

i'm going to try to disable the DNS Client all together and reboot. let's see how that works. :dots:

[Vexx]

You might also complain upstream to your ISP that you think their DNS caches are poisoned or they're getting bad DNS resolve data from someone further upstream who is poisoned.

Instead of righteously seeking the true correct answer to a DNS resolve query, most DNS servers keep a cache of previous request results for efficiency; they *should* flush periodically but sometimes administrators set the flush to something silly like "once every week".

One time something between me and Animesuki kept a poisoned cache for almost a week :P and calling my ISP is always an exercise in homicidal rage ("yes sir, we're going to spend 3 hrs asking you if your computer is plugged in") ....very annoying.

[Gear853]

interesting enough, when i disable the Internet Information Server Manager (Via Administrative Tools) i get this instead (http://i6.photobucket.com/albums/y208/Gear853/message.jpg)..

:twitch:

[SeijiSensei]

What if you use a mirror (http://animesuki.rut.org/mirrors.php)? For instance, I use animesuki.rut.org (http://animesuki.rut.org/) rather than www.animesuki.com. I notice with some amusement that the mirror I use no longer appears in the list of mirrors.

Might I suggest you take a look at your HOSTS file? It lives somewhere under C:\Windows. Occasionally a piece of malware will add entries to that file because it overrides DNS resolution. Make sure there are no stray entries for www.animesuki.com. It's not too likely, but it's worth a quick look.

The other symptoms you describe suggest that all outbound HTTP requests are being redirected to the local machine. It's as if everything resolves to 127.0.0.1 ("localhost"). When you had IIS running, it answered those queries; when you turn it off, they fail. I don't how you could get into such a conundrum, but then I haven't used Windows in a very long time.

If you can bring up a terminal with Start > Run > type "cmd" + hit enter, try pinging various remote locations and see what IP addresses you get back. Start with "ping www.animesuki.com" and make sure it resolves to 69.42.221.126. If it doesn't, something is mucking around with your DNS resolution. If it does resolve correctly, but you can't get there with IE, try installing Firefox and see if that works differently.

[NightWish]

I notice with some amusement that the mirror I use no longer appears in the list of mirrors.It is all relative. The list of mirrors you see depends on where you are viewing the list.

[cyth]

Try OpenDNS for new DNS servers. That way you'll bypass your ISP DNS servers feeding you crap.

[Proto]

If I may ask, why does it make you sad?

As a GNU advocate you couldn't expect less from me :p (yes, I know Apache isn't under the GNU license, for anyone that feels making a cheeky remark)

Anyway if this is the only page with which you are having problems you may be better off just bookmarking that IP and relying on that for a while until the DNS server that is causing the problems stops going bullocks.

[Gear853]

What if you use a mirror (http://animesuki.rut.org/mirrors.php)? For instance, I use animesuki.rut.org (http://animesuki.rut.org/) rather than www.animesuki.com. I notice with some amusement that the mirror I use no longer appears in the list of mirrors.

Might I suggest you take a look at your HOSTS file? It lives somewhere under C:\Windows. Occasionally a piece of malware will add entries to that file because it overrides DNS resolution. Make sure there are no stray entries for www.animesuki.com. It's not too likely, but it's worth a quick look.

The other symptoms you describe suggest that all outbound HTTP requests are being redirected to the local machine. It's as if everything resolves to 127.0.0.1 ("localhost"). When you had IIS running, it answered those queries; when you turn it off, they fail. I don't how you could get into such a conundrum, but then I haven't used Windows in a very long time.

If you can bring up a terminal with Start > Run > type "cmd" + hit enter, try pinging various remote locations and see what IP addresses you get back. Start with "ping www.animesuki.com" and make sure it resolves to 69.42.221.126. If it doesn't, something is mucking around with your DNS resolution. If it does resolve correctly, but you can't get there with IE, try installing Firefox and see if that works differently.

something is messing around my DNS resolution. it just ping back to local host instead.

and this is the only site that's having problem at the moment, i just like to get it resolve before i found more site...that's doing the same.

[Proto]

Now if it effectively pings back to your local host then the problem is on your side. (just to confirm, try a traceroute as well). Check the hosts file as SeijiSensei instructed. For some reason or another there should be an entry for animesuki there.

[WanderingKnight]

something is messing around my DNS resolution. it just ping back to local host instead.

Rerouting to localhost is the classic way to disable DNS resolution with the hosts file (usually done to prevent an accidental connection to a malware-ridden website). If I wanted to write some malware to annoy simply annoy people, rerouting * to 127.0.0.1 would be a pretty funny way to mess with the infected machine.

Check your hosts file as indicated by Seiji (Windows\system32\etc\hosts?).

[GHDpro]

I did a test on intoDNS.com (http://www.animesuki.com/) to see if any of the AnimeSuki DNS servers might be out of date, but that doesn't appear to be the case. Plus, I suspect we'd get a lot more complaints in that case.

I second the suggestion to use OpenDNS (http://www.opendns.com/). When your provider's DNS servers are working properly OpenDNS is not really required, but it might be worth a try in this case.

As already mentioned by NightWish: none of the servers associated with AnimeSuki runs Windows. The site (animesuki.com) runs lighttpd (BSD license) on FreeBSD. The forum also runs lighttpd on CentOS (free version of Red Hat Enterprise). Apache tends to use huge amounts of RAM when serving moderate amounts of visitors unless you use the threaded MPM. However last time I checked (which is a while ago) the threaded MPM doesn't work well with PHP. Hence we use a lighter alternative called lighttpd. If I had to rebuild one of the servers at this time I'd also might give nginx a try (nginx already runs ImageHost.org (http://www.imagehost.org/), one of my other sites).

PS. Sorry for the slow response from my side, but I'm still waiting for my ADSL to be reconnected after moving recently.

[Gear853]

i removed the entry of animesuki.com in my host file and now it works! YAY!

thanks for all your help!

*hug hug hug*

[CrowKenobi]

I tried to log out of the forum, and after some time of inaction, this (what I'm assuming to be) error log appeared:

<br />
<b>Fatal error</b>: Maximum execution time of 30 seconds exceeded in <b>Unknown</b> on line <b>0</b><br />:confused:

EDIT: Browser is Firefox 3.0.6

[NightWish]

I tried to log out of the forum...The PHP interpreter (http://www.php.net/) stops, generating that error message, after running for ~30 seconds, if it has not completed its task, to prevent scripts from running forever if there is a problem. It would appear that the forum's design means that such error messages cannot always indicate what was running at the time; hence the, "unknown at line 0". The other output was HTTP (http://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol) headers followed by a compressed copy of the page (http://en.wikipedia.org/wiki/Gzip#Other_uses).

We have a copy of the error in the logs, so I wouldn't worry about it too much unless it happens frequently.

[SeijiSensei]

i removed the entry of animesuki.com in my host file and now it works! YAY!

Now the question you need to resolve is how your HOSTS file got corrupted in the first place. Were there other bad entries there as well or just www.animesuki.com? Did someone edit the file while you weren't looking just to annoy you as an AS member? It seems unlikely that malware would only create an entry for AS; it sounds more like a prank to me. Still it's worth giving some thought to how that file was mangled, and perhaps also by whom.

Hugs are nice, but cookies are yummier.