Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Creating real sub domains for IIS, not just redirects

Status
Not open for further replies.

egotek

Programmer
Jul 23, 2003
29
US
OK, I'm running Win Server 2003 now and I want to be able to setup a sub-domain (not even sure if that is the correct terminology for it!). Anyway, I currently has the server as a DC, exchange server and web server, and have my domain setup on it. I want to be able to have sub domains, such as or forums.mydomain.com, etc.

I've tried setting up new sites under IIS and new dns zones and just can't seem to figure it out. I've also search through the forums here and haven't found anything to helpful as of yet. Any insight on this would be much appreciated.
I have full access to my server (obviously, it's mine) so I can do whatever is needed.

Thanks,
Michael
 
You will need to setup headers within IIS for the sites to work, then setup alias on your DNS server to point to the webserver box.

 
OK, I've got the headers setup in IIS...think. I set it up as mail.domain.com (domain being my actual domain name). I went into the DNS admin tool and created a new alias under the domain.com listing. Named it mail, FQDN showed as mail.domain.com and I put the host as the ip address for the server. Is this correct? If so, does it take some time to update cause I tried going to the site as just and it wasn't able to find the page.

Thanks again,
Michael
 
mail.domain.com is resolving to localhost 127.0.0.1. so when you try to resolved this it will just point at the client machine instead of the web server. For the target host you would need to put the FQDN of the web server.

When you add/change a domain alias/pointer or any other thing it can take time to work usaully max of 48hrs but if your using that DNS server as your primary DNS for your client machine then it should work pretty much right off.

 
Well I'm running exchange, IIS & DNS all on one server, which is also the domain controller. So I have the DNS alias pointed to the IP address of the server. Should I maybe change it to the FQDN of the server rather than the IP address? (Don't really see why it'd make a difference, but...)

Just you give you a little background, may help out. I running this from home on a cable connection. I have my initial DNS for my domain setup on mydyndns.org...

Oh you know, I wonder if I need to set the Alias to point to my actual cable ip address....
 
ahh nice, it works now. I just pointed it to the servers FQDN, which I thought I'd done before....probably didn't have IIS setup correctly when I did that though.

anyway, thanks for your help, I really appreciate it.

Michael
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top