I've got three web sites each with its own domain going to my one Windows Server 2008 IIS 7.0 web server.
example1.com
example2.com
example3.com
The site bindings for each:
IIS 7.0 Site Bindings example1.com http://img371.imageshack.us/img371/4215/example1pf4.gif
IIS 7.0 Site Bindings example2.com http://img371.imageshack.us/img371/2567/example2xx0.gif
IIS 7.0 Site Bindings example3.com http://img266.imageshack.us/img266/8186/example3rh9.gif
When I navigate to example1.com, then I see my example1 web site.
When I navigate to example2.com, then I see my example2 web site.
But, when I navigate to example3.com, I see my example1 web site--not the example3 web site I expect.
What's going on? Why might example2.com work, but example3.com fail?
Issue resolved!
I removed and then recreated the example3.com web site within IIS and it's now working.
I didn't change anything. It either originally had a simple typo or the act of recreating it just happened to fix a hiccup within IIS.
It's stopped working again after I setup additional redirects within IIS forcing web sites to use sub domains:
http://example1.com/ redirects to http://www.example1.com/
I've again removed and then recreated the example3.com web sites; I've reset IIS; I've rebooted the server. It's still not working correctly.
I've figured it out. It's not an IIS issue. It's a DNS issue.
The example3.com traffic is for some reason directed to a web server at a different company. THEY serve up a page with only an HTML frame on it. That frame loads a page with the address http://example3.example1.com. That's what I need to handle on MY web server.
I would validate that you have example3.com pointing to the proper location on disk. Also ensure that it is not stopped.
The fallback to example1 is due to the binding entry with no header value.
Related
I just started looking at IIS on Windows10.
I have a stupid question. I added a binding to Default Web Site ("www.test.com") in IIS Manager.
I was expecting to see the default page when browsing to this url, but it took me instead to an actual existing page.
Can anyone explain me why?
If you've added www.test.com to your bindings, clients (like your web browser on the same system) still don't know that IIS hosts the site.
see this: Setting up a Host File - Faking URLs
This is useful when dealing with multiple sites:
Site 1:
test.com
www.test.com
www2.test.com
Site 2:
another.url.com
with just listening to a single IP, you cannot control which request ends up at which site, this is what the binding solves
I have a problem i cant seem to understand in IIS 7.5, OK here goes...
I have a website www.mysite.com that's hosted on my ISP, i have a sub domain drones.mysite.com that gets directed to my home server at IP address 1.1.1.1 which is managed by IIS on a windows 7 PC, i also have another sub domain of cloud.mysite.com that also get directed to 1.1.1.1, again looked after by IIS BUT i have a linux/apache server (on a seperate PC) and i want shop.mysite.com to be directed to the IIS server then redirected internally to my linux server.
From what i've read it needs to be done through HTTP redirect but i don't want to lose my original directed sites.
Any ideas, cheers in advance
Mark
I have a Windows Server 2012, with IIS 8 installed. I have multiple websites there. I also have the Default Website.
When I create a new website like www.abc.com and abc.com, it works fine. However, when a customer enters an invalid subdomain to abc.com (a subdomain definition that is not actually there), like xyz.abc.com, it automatically redirects to my Default Website which is a landing page.
Instead, I want to return a custom 404 page from IIS. Is that possible?
Thanks.
Your DNS should be taking care of that. If xyz.abc.com doesn't exist in the zone, no browser should be coming even close to IIS.
That is, unless you have a wildcard record configured. It sounds like you might.
Give it a look.
I have a problem where when I go to my website it comes up with a redirect loop. I've tried clearing the URL Redirects from the IIS Admin Console in the web control panel from my hosting provider and I've also tried removing the httpd.ini file from the site root directory to try and clear all re-directs, but for some reason when I go to the site it STILL wants to redirect in an endless loop. The site is agrionline.biz
Before i did anything I had a subdirectory domain pointing set up which made http://agrionline.biz actually use agrionline.biz/site1/ as the root folder.
I wanted to change this so that instead of that I wanted my site to actually redirect to the site1 folder, rather than use it as the root. So I went into the IIS Admin Console on my hosting providers web control panel and tried to add a URL Redirect from '/' to '/site1/'. Then i went to the domain pointing admin page in the hosting providers web control panel and deleted the domain pointing. Anyway after doing all this, the site is now stuffed and if I go to back to both these areas and clear the redirects and the domain pointing and even go and remove the httpd.ini file that was created, the site still incorrectly re-directs!
What can I do to resolve this? Any ideas? Has anyone experienced this before on a shared hosting account without direct access to IIS.
From the control panel it says my server platform is Windows 2008 Server Enterprise.
I have an application that is currently deployed (ex. www.example.com ). However, now we have a "secure" subdomain, which will take all of the requests that need to be encrypted (ex. secure.example.com). The site that is at www.example.com is currently mapped to C:\inetpub\example.com\wwwroot\, and I've mapped secure.example.com to C:\inetpub\example.com\wwwroot\secure.
However, since secure.example.com was setup as a new website within the IIS Manager, when the secure site is visited, it displays an error since there is no web.config associated with this website; however, this is the way I want it since I want this to be a part of the application that is in the parent directory.
I think what you really meant to do was just right click on the web site for example.com and edit the bindings. In there you can add host names to that site.
Make sure you add them for port 443 which is SSL.
Map both the IIS virtual directories/web sites to the same directory, and check that are both using the same IIS application name.
(Not tried this, but can't recall seeing anything to say it would not work.)