Point domain test.mywebsite.dk to some other IP or delete that domain if not required.
Main Topics
Browse All TopicsHi I have just deleted my "test.mywebsite.dk" so I now only have "www.mywebsite.dk" left.
That means that I can of course not access "test.mywebsite.dk" anymore..
BUT.. the strange thing is.. I can STILL access the SSL encrypted version at "https://test.mywebsite.dk
Any ideas?
I know that the problem is located on the IIS 6.0 server somehow, since if I deactivate SSL 443 for "www.mywebsite.dk" in IIS, then IE on the client says that the webpage cannot be found.
I have also cleared the recycling of the App. Pool for the website - it didnt help.
Is it a bug in IIS 6.0? Or related to the star *-alias SSL certificate?
Or something else?
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
I assume you're not deleting the dns record and you're expecting a 404 error because you deleted the site from IIS. ssl by default doesn't use host headers in IIS. So if test.mywebsite.dk resolves to 10.11.10.100, requesting https:\\test.mywebsite.dk in your browser is the same thing as requesting https:\\10.11.10.100. That said, if both test and www were using the same IP address, than IIS is using the www site to process the request.
The only way to get rid of test is to delete that record from dns. If you have already done so, you may need to wait for the "time to live" to expire and the change to propogate the internet.
The reason why I find it particular strange is that the host header value for the website has ONLY the "www.mywebsite.dk" - it DOESNT have "test.mywebsite.dk".
So, what if I want both websites running on the same machine with same IP, but as 2 different websites. Is that not possible at all? Because it doenst know if it should use the "www" or "test" version? Even though I have a * alias SSL certificate - that should be able to work with 2 (or more) websites?
Yes I would delete the "A" or "CNAME" record you have in dns for "test". You can add it back later if you want.
IIS sites without SSL must be unique amongst ip, port, and host header. The latter two are what let you host multiple sites with a single ip address.
With SSL, the header is INSIDE the encrypted request, so IIS can't look at the header to see which site it should route to the request to. All it has to go by is the IP.
http://support.microsoft.c
However, there is new (but not default) functionality in IIS 6.0 or later to use host headers in ssl:
http://www.microsoft.com/t
The only thing that strikes me as odd about this is that I think you should be getting a "bad request" if the www site is configured with JUST a host header. This makes me believe the www site is also configured without a host header. I'm not sure about this but it's worth a look.
Thanx for all the info..
The www-site IS having a host header set to www.mywebsite.dk.
Ok, so I hear You saying that because I have hadware firewall that only allows 1 IP coming through and because SSL's webpage information is inside the certificate, it doenst use the webpage header info in IIS, but let the request go through anyway bacause dns for test and for www is the same. ok.
Hmm.. Do You know if its possible in a hardware firewall then to direct requests to test.* to one server and www.* to another? Even that they have the same external IP ? but 2 different internal IPs?
And what will happen if I do as You told.. deletes the dns record.. and open it again, then the "problem" will appear again right?
Will it be possible to have both test AND www websites running on the same machine then?
I mean.. if SSL cannot find out which webpage to stick to when just having "one", - then how will it be able to distingues between the 2 different websites test and www?
How should I set it up, if I want to run both websites on 1 server?
Another strange thing is that recently it counts the online users wrong.. its like its doubling up!
Maybe it have something to do with this "not being able to know which website it belongs to" when it comes to SSL
From the info given so far, this shouldn't have anything to do with your firewall. My assumption to here is that your firewall is merely forwarding http AND https traffic to your IIS box.
The second link in my earlier post describes how to run ssl sites with host headers which would allow you to run multiple ssl sites with a single IP.
An application layer aware firewall could do the forwarding you described (ISA server for example). But the same restrictions regarding SSL and host headers my apply to it.
If you delete the record and then put it back everthing will be as it is now so yes you'll still get the problem. Deleting a dns record isn't going to "clear" anything in this case.
Business Accounts
Answer for Membership
by: Jones911Posted on 2009-04-23 at 05:09:26ID: 24214079
cached DNS entry. Try open cmd promt and type ipconfig /flushdns