Built a brand new server, with a fresh copy of Windows Server 2003 Enterprise x86 Edition.
Installed the .NET Framework 1.1, 2.0, 3.5, and 4.0
Added the "Domain Controller" and "Application Server" roles.
Created a new website, pointed it to a local directory: C:\Inetpub\angryoctopus.net\
Added the appropriate headers: angryoctopus.net, www.angryoctopus.net, TCP port 80, all IPs
Moved the website content into the local directory.
Configured the default document in IIS: Default.aspx
Enabled ASP.NET for this website, and set it to the correct version: 2.0.50727
Configured the zone angryoctopus.net in DNS. Tested DNS lookup here to ensure DNS was functional.
Opened website in VS 2008 and re-built (and debugged) to ensure the content was functional.
I can clearly see that IIS is responding normally, by browsing directly to my server's IP address. Since this does not use the angryoctopus HTTP header, the default website is displayed instead: the "Under Construction" page.
And yet, after all of this, angryoctopus.net still returns 404.
Does anybody know what could be wrong? What troubleshooting steps have I forgotten? Is there a command-line diagnostic that might provide more information?