Hey Jeff, I was wondering. Does it make sense to set up an apache server and using the virtual machine option to point to each of my boxes. What I was thinking doing this, but instead of pointing each address to a folder, I might be able to point it to a IP address on the local lan. That way, I do not need separate IPs for each machine.
I have seen this done, but I have not tried it. I didnt really want to get into it if it were not possible. I know I can add a secondary DNS to the dd-wrt router, and I was thinking this would be a good way to go. Chris Penn... On 5/22/07, Jeff Lasman <[email protected]> wrote:
On Monday 21 May 2007 09:45 am, Chris Penn wrote: > I have been trying to get one of my domains , fuckmicrosoft.biz, > which is point to my house, to resolve to different machine in my > home using different subdomains. I have setup the local dns on a > dd-wrt router and it is resolving, as far as I can tell, locally. I > am pointing this domain name at zoneedit.com's Name servers and then > creating a record pointing to my dd-wrt router via the home IP. > Again, zoneedit.com is just being used to sink the IP with the > router. > > What I am trying to do is get the subdomains pointing to each > computer in my house and resolving from the outside, ie)ssh > puter1.fuckmicrosoft.biz from school will allow me to ssh into my > computer1 at home. > > Any advice would be great and if it is impossible it would be great > to know. What you need to do is have dynamic DNS (from any provider) point to your router's public IP#. Then the problem is you have to route the oustside stuff through to your home system. Does each of your home systems have its own public IP#? Probably not. Which means it has NATted IP#s. Presuming that you have to tell your router that everything that comes in on a given IP#/port pair from the outside, gets routed to the IP#/port pair of the correct machine. If you want different subdomains to go to different machines but only have one public IP# answered by the router, then you probably need to use a router that can route based on host-headers (you may have to write your own <wry grin>). Or get multiple IP#s from your provider and put the machines outside your router-firewall (which is what we do; I have five routable IP#s at home; one for my router, four left for other systems, which of course have to be hardened as if they were at a datacenter, because they're directly on the 'net. I hope I've been a bit of help. Jeff -- Jeff Lasman, Nobaloney Internet Services P.O. Box 52200, Riverside, CA 92517 Our jplists address used on lists is for list email only voice: +1 951 643-7540, or see: "http://www.nobaloney.net/contactus.html"; _______________________________________________ 909linux mailing list [email protected] http://909linux.org/cgi-bin/mailman/listinfo/909linux
-- "As we open our newspapers or watch our television screens, we seem to be continually assaulted by the fruits of Mankind's stupidity." -Roger Penrose
