Results 1 to 5 of 5
Thread: Personal network DNS
|
Enjoy an ad free experience by logging in. Not a member yet? Register.
|
|
-
02-15-2007 #1
Personal network DNS
I currently have port 80 forwarded to my webserver, so when I type javasnob.homelinux.net in my browser, the default page for my server comes up. So far so good. The thing is, I want it so www.javasnob.homelinux.net goes to my webserver, TheRing.javasnob.homelinux.net goes to my main machine, etc.
In order to do this, do I need a special feature in my router, or can I tell it to point to a BIND server I have set up, or something other solution I haven't thought of?
Thanks!Flies of a particular kind, i.e. time-flies, are fond of an arrow.
Registered Linux User #408794
-
02-15-2007 #2
It depends on whether you are accessing it from inside or outside your
network. Inside, either you run BIND on one of your machines and point
your other boxes to use it as the name server. Outside your own network,
you need to configure the dynamic dns provider, Dyndns or whoever.
-
02-15-2007 #3
This would be from the outside. javasnob.homelinux.net is registered with DynDNS, but I'm not sure how to use DynDNS to manage my personal network.
Flies of a particular kind, i.e. time-flies, are fond of an arrow.
Registered Linux User #408794
-
02-15-2007 #4
That doesn't work. You have ONE external DYNDNS name with one associated IP address. Now you want to be able to access internal hosts which use internale IP addresse (192.168.0.... or 10.0. ...) which cannot be propagated to the outside net.
The only way I see to get this done would be to set up a VPN."Really, I'm not out to destroy Microsoft. That will just be a completely unintentional side effect." Linus Benedict Torvalds
-
02-16-2007 #5
There is another way. It's quite convoluted, so bear with me. Have all your domain addresses (<whatever>.javasnob.homelinux.net) point to your dynamic IP address using your DynDNS service.
Get your server installed with Apache and set up Virtual Hosts for each machine.
Make each virtual host point to a NFS-mounted share from the machine in question.
At least this way, you dont have to run apache on each machine, and have to bolt it down numerous times.Linux user #126863 - see http://linuxcounter.net/