Dreamquick
msg:949183 | 12:06 pm on Oct 7, 2003 (gmt 0) |
If you're running something like ASP on the site you can just check the HTTP_HOST header that the browser issues via Request.ServerVariables, and if it's not in a set list then issue a redirect to the domain you actually want them to go to. - Tony
|
pageoneresults
msg:949184 | 12:06 pm on Oct 7, 2003 (gmt 0) |
It sounds like they are not familiar with how to set this up without using another IP. You might want to direct them here... Redirect a domain such as example.com to www.example.com [xoc.net]
|
tomapple
msg:949185 | 1:56 pm on Oct 7, 2003 (gmt 0) |
PageOne, Actually I had provided them the same link you mentioned. After which they came back to me with the reply in my original post.
|
plumsauce
msg:949186 | 5:00 am on Oct 8, 2003 (gmt 0) |
The link given to you by pageoneresults should work
flawlessly. Your host is correct in that they need to setup
an additional site, but that is it, other than
the remaining directions from the linked article. They do not need to give you an additional ip, or
change your dns. Guess you need to have another try at them while
speaking very, very slowly. ++++
|
tomapple
msg:949187 | 4:48 pm on Oct 8, 2003 (gmt 0) |
My understanding is that both www and non-www were already setup on the IIS server. You can enter either www.domain.com or domain.com in a browser and both work exactly the same(the only difference being the lack of "www"). What my provider seems to be indicating is that there is a difference in how their servers/IP addresses are configured versus the configuration of the server setup on the example page.
|
plumsauce
msg:949188 | 8:50 pm on Oct 8, 2003 (gmt 0) |
You are correct, the dns resolution for your
domain will work correctly, and to the same
web site, if either the site is set up with
no host headers, or both host headers. Since they use a dedicated ip for you,
they are probably using no host headers. What the tutorial is suggesting is that
a second site be set up to implement
the redirect. What I am further suggesting is that the
second site can use the same ip. But,
have a host header of example.com, which
then redirects to www.example.com. The work involved for your host is no
more than setting up a second blank
site pointed at your original content
with a redirect. They are just not getting it. ++++
|
|
