Jonathan de Boyne Pollard said:
SD> On my internal network I can access
http://www.xyz.com,
SD> but I can't access
http://xyz.com.
Then you have a seriously strange problem, given that both of the domain names
in those URLs map to the same IP address:
[C:\]dnsgeta xyz.com.
199.26.172.28
[C:\]dnsgeta
www.xyz.com.
199.26.172.28
[C:\]
SD> How can I redirect
http://xyz.com to
http://www.xyz.com
SD> without using IIS HTTP headers?
That's not something that is up to you. It's something that is
up to Michael Galassi, the owner of "xyz.com.". He has in fact
already configured things appropriately for those two URLs to
result in the same page being displayed. If this is not happening
on your network, then you've had to take explicit action and in
fact work pretty hard to make it not so. As such, I suggest that
you simply undo what you have done.
He said PRIVATE network. On your PRIVATE network, you can run any domain
you want on your PRIVATE DNS Server although running a domain with a trade
mark might get you into hot water but it would not have any technical
issues, just legal ones. However, an attorney may argue that since it is
private, it is not in conflict with a trade mark. Notice, this doesn't
apply to personal use of weed. Probably because weed it not trade marked!
(O:=
You can also use any IP address you want on your PRIVATE network but note
that you will not be able to route to the Internet with it. The naming will
also restrict what you can do with a public network. If you called your
private network xyz.com then your PRIVATE DNS would point xyz.com to your
PRIVATE DNS server or web server. You could then put in an entry of
www.xyz.com which could point to the public domain owned by Michael Galassi.
I don't see anything wrong with that. However, you could not have a local
email server that routed mail to the Internet with your reply-to as
(e-mail address removed) because THAT would get you into trouble. If it were used
strictly for internal use, then technically it's not a problem but legally,
only your hair dresser and your lawyer know for sure.
You can also call your dog Hillary Clinton which might get you on the
tonight show but there's not much Hillary Clinton, NY Carpet bagger, could
do about it.
The reason you cannot get to xyz.com but you can get to
www.xyz.com on your
PRIVATE network is because you don't have a blank host address entry
pointing to xyz.com on your PRIVATE network.
If you're going to do any mixing with PRIVATE and PUBLIC networking, then
it's best to have something legitimate, as Jonathan so eloquently pointed
out.
HTTP headers is HTTP Host Headers and it is used to point to different web
sites hosted on the same server with the same IP address.
This can be done in ASP when you use Request.ServerVariables("SERVER_NAME")
and have your default page decide if someone is trying to get to the main
web site or perhaps your forum site.
domain.com /
www.domain.com
or
forum.domain.com
Assigning a variable and then branching to a subroutine to write the default
page would correctly point the user to where they wanted to go, all on the
same web site.
--
Roland
This information is distributed in the hope that it will be useful, but
without any warranty; without even the implied warranty of merchantability
or fitness for a particular purpose.
