Forum Moderators: open
I run a colo Win2000 server that relies on my colo hosts DNS servers, so do I ask the host to create a DNS entry for UK.XYZDomain.com? If so, any related DNS issues that might catch me by surprise?
On my Win2000 colo server I'm using host headers and a single IP address for multiple domains, so how would I set up the subdomain?
Do I go through the standard Win2000 procedure to create a new virtual directory that responds to uk.xyzdomain.com www.uk.xyzdomain.com?
Thanks for any help.
If you want the user to use the same web-application, but with settings based on a specific entry point, point all possible host headers to the same web-app in IIS and detect the current host header from within your code. Based on the outcome of the detection, you can 'personalize' your web-app
Good luck!
I'm left with the question: Is there anything that needs to be set up in the co-lo hosts DNS?
Do you know if http requests simply resolve to the DNS for XYZDomaina.com and then, routing to the subdomain is simply handled at the IIS level, as if a sub-domain is "the same" as a sub-directory?
Thus, for example.com, you would normally have:
host record = example.com
alias record = www = example.com
now you want to add:
alias record = web2= example.com
or
alias record = sub.web2= example.com
all of the above are silly examples,
your names will be something else.
Your other alternative if you are talking:
a.b.example.com
is to do a sub-delegation.
You will know that the dns setup is correct
when you can ping it by the new name.
added:
the reason you need to do this is that the
client needs to be able to translate the
name into an ip address.
++++