+1 - This is really weird. Just to add to the problem desription, I notice that even linking to static files (dartmouthplayers.ns.ca/css/common.css) gives out a 500 error. I've never seen a static file give an error 500 before.
–
Mark Henderson♦Aug 30 '10 at 21:33

4 Answers
4

A 500 error is generally associated with an entry in your Event Log which should shed some light on what is happening. Have a look there, and perhaps update your question with the error, and we can help debug it.

Simple but easilly overlooked - do you have other websites running on the IIS?

If so, could one of them accidentally be bound to the same website (the non-www variant)? IIS normally warns you if you try to do this (you get a message about duplicate bindings), but it doesn't actually stop you.

This sounds like a good possibility, if you do have multiple sites configured, try stopping the one that you are trying to have dartmouthplayers.ns.ca go to and try loading the two domains again. If you still get the 500 but the www. doesn't load, you are getting a different site.
–
ManiacZXAug 30 '10 at 22:05

I just tried this out on my IIS7.5 server and it automatically stopped the website with duplicate bindings when I tried to force it, so this might not actually be the case.
–
Mark Henderson♦Aug 31 '10 at 3:13

HTTP version 1.1 allows multiple websites with different hostnames to share the same IP address (with each one possibly serving different content). The client sends a "Host:" header indicating which hostname it is trying to access, and the web server has to determine what content to serve for that hostname.

Consequently, independently of the DNS configuration, the web server has to know all the hostnames that can be used to connect to the server, and what content to serve for each one. So you need to find that configuration in your web server software.

If that's not enough of a hint, tell us what web server software you use.

-1. He is using IIS. Obvious from the window and the named OS makes it highly likely anyway.
–
TomTomSep 2 '10 at 7:49

@TomTom It's not obvious from the window. There's nothing in the window that says IIS. There was nothing in the question that said IIS. The only way it's obvious is if you've used IIS and know what its interface looks like. I haven't. Sorry. I didn't know that was a prerequisite for trying to help here.
–
coneslayerSep 3 '10 at 18:56

You boviosuly have not a lot of experience with IIS 7 ;)
–
TomTomSep 4 '10 at 10:54