Configure domains on a network

Goal: I am trying to build a home network and would like to have external domains point to specific computers/servers on my network. Current set up: I have a dynamic IP provided by my broadband ISP. I found a company that provides Dynamic DNS services and subscribed to them. The name of the company is no-ip.com. I can use [login to view URL] as my DNS provider to always point my websites, for example, [login to view URL] and [login to view URL], to my home network. The no-ip application is running as a service on the computer with name Server01 (network IP [login to view URL]) Problem: If port 80 is forwarded by my router to Server01 ([login to view URL]) and [login to view URL] resolves to Server01 (same being with remote desktop), how do I get [login to view URL] to resolve to a completely different server, for example, Server02 (network IP [login to view URL]). So if I where outside the network, I would be able to remote desktop protocol into [login to view URL] or [login to view URL] and get into different computers. Same goes with going to those URLs in a browser pointing to different web apps on different servers running Apache. I would like somebody to log into my server and configure this as well as tell me how it is done. thanks! :) ****UPDATE: I am now receiving comments from people saying that this is not possible, that would have to forward different ports for each server (example [login to view URL] and [login to view URL]). I don't want this like this. I find it hard to believe it is impossible. Out of curiousity, how do web hosters do it? I doubt they have one router for every server they have. Let me know what needs to be done and I will do it. ## Deliverables 1) Complete and fully-functional working program(s) in executable form as well as complete source code of all work done. 2) Deliverables must be in ready-to-run condition, as follows (depending on the nature of the deliverables): a) For web sites or other server-side deliverables intended to only ever exist in one place in the Buyer's environment--Deliverables must be installed by the Seller in ready-to-run condition in the Buyer's environment. b) For all others including desktop software or software the buyer intends to distribute: A software installation package that will install the software in ready-to-run condition on the platform(s) specified in this bid request. 3) All deliverables will be considered "work made for hire" under U.S. Copyright law. Buyer will receive exclusive and complete copyrights to all work purchased. (No GPL, GNU, 3rd party components, etc. unless all copyright ramifications are explained AND AGREED TO by the buyer on the site per the coder's Seller Legal Agreement). * * *This broadcast message was sent to all bidders on Wednesday Dec 20, 2006 5:35:05 PM: Greetings to all bidders, I must say, I never imagined that this project wouldn't be as easy as a small DNS configuration. Almost all of you have come up with different suggestions. Some of you have said that Apache can be configured to solve this problem with a Name Virtual Host, but my thought is that this will only work with website hosting on port 80 and not for other ports for things such as ftp, smtp, rdp, and so on. Let me know if I am wrong. So say the least, I don't want to install $500 software to accomplish this. If anything, and all else fails, I can go to my broad ISP and ask for a business account that has extra IP addresses. ## Platform Router: NetGear FVS318. Server OS: Windows 2000 Server SP3. using Windows DNS.