Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have a site on my server that only works with a www. example: works but without it, it does not.

But the site's bindings has both listed:

alt text

and the DNS has the blank host record: alt text

What did I not set right?

It's odd because: - returns a 500 error and - returns a server not found error


update: My event log has this error each time I try to access that domain:

Log Name:      Application
Source:        Microsoft-Windows-IIS-W3SVC-WP
Date:          9/2/2010 10:36:52 PM
Event ID:      2268
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      WIN-R092323U23
Could not load all ISAPI filters for site 'DEFAULT WEB SITE'.  Therefore site startup aborted.
Event Xml:
<Event xmlns="">
    <Provider Name="Microsoft-Windows-IIS-W3SVC-WP" Guid="{670080D9-742A-4187-8D16-41143D1290BD}" EventSourceName="W3SVC-WP" />
    <EventID Qualifiers="49152">2268</EventID>
    <TimeCreated SystemTime="2010-09-03T02:36:52.000000000Z" />
    <Correlation />
    <Execution ProcessID="0" ThreadID="0" />
    <Security />
    <Data Name="SiteName">DEFAULT WEB SITE</Data>
share|improve this question
+1 - This is really weird. Just to add to the problem desription, I notice that even linking to static files ( 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
Are you using any URL rewriting? – Mark Henderson Aug 31 '10 at 3:14
up vote 1 down vote accepted

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.

share|improve this answer
+1 - exactly. This is an in application error. THe client ends up SOMEWHERE (on the server). Event log should have crash information. – TomTom Sep 2 '10 at 7:49
actually, I spelled it wrong on the binding without the www. There is no "h" in the name :) – aron Sep 3 '10 at 2:48
Well done - glad you got it figured out. Something so simple! – Mark Henderson Sep 3 '10 at 3:32
Hahaha. I did actually look at the picture to see if that was a problem, but "Darth" parsed so I didn't think any more about it :) – crb Sep 3 '10 at 14:43

This is good info. We know DNS is working if you're getting 500s. A 500 means your client is resolving the correct IP and that the server is throwing a 500 in response to the inbound HTTP request.

@coneslayer: The screen shot appears to be that of IIS bindings and the title of the post "Windows..."

So I don't believe you have an IIS configuration issue. It appears, from what we see so far, an application problem.

What is your default HTML file settings and is there some ASP/.NET or JavaScript within that is causing the 500 to be thrown?

Maybe throw up your web.config

share|improve this answer
It's not a web.config, default file, or javascript issue. It just seems like the site is resolving to the server, but NOT the correct website. – aron Aug 30 '10 at 21:13

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.

share|improve this answer
This sounds like a good possibility, if you do have multiple sites configured, try stopping the one that you are trying to have 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. – ManiacZX Aug 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
thanks, I'll check into this – aron Sep 1 '10 at 15:52

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.

share|improve this answer
-1. He is using IIS. Obvious from the window and the named OS makes it highly likely anyway. – TomTom Sep 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. – coneslayer Sep 3 '10 at 18:56
You boviosuly have not a lot of experience with IIS 7 ;) – TomTom Sep 4 '10 at 10:54

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.