Here are some guidelines for running a private web server on your home network for internet accessibility. I think I've included everything. This is actually what I am using myself (am running NetBSD) and it is working: 1. Use Dynamic DNS and a 3rd party DDNS service provider like dyndns.org. There should be an entry for DDNS in your home cable/DSL router for this. You don't need an internet registered domain and DNS address - the DDNS service will do it. You don't need a static IP address from your ISP for your router. 2. Install and run the SSH daemon for remote admin to your web server. 3. On remote Windows PCs use PuTTY and PuTTY's command line utilities for up/downloading files from your web server. 4. On your cable/DSL home router put an entry for the remote IP addresses in your firewall, specifying the host and SSH ports, and route them to your web server. 5. Put an entry in your router's firewall for the router itself, as in the previous step, to test internet accessibility from your home network. If you put an entry for your web server's host name in a home network PC's hosts file, you will access the web server without going out to the internet. If you use the web server's FQDN (full host plus domain name, fully qualified domain name), your home PC will actually request name translation from your ISP's DNS, which is your router, and then direct your request to your router's WAN side port, effectively testing for internet accessibility. 6. In your web server's host file put your DDNS address and FQDN (full host plus domain name, fully qualified domain name) you got from your DDNS service provider. Don't put in the web server's private LAN address. Note the IP address may change because you are using DDNS - but it doesn't change that frequently - so you may want to run a script that checks it daily. 7. You may want to put a simple non-dotted up-to-15-character name for your ISP's DNS to test name resolution from your web server when you have problems using nslookup for example (you have to specify the server using nslookup because the web server is on your home network). 8. You can also put a simple non-dotted up-to-15-character name (say, just the host name only of the FQDN) for the web server in your home PC's hosts file to permit local testing of your web server. 9. In rc.conf (I am running NetBSD) on the web server, put in the DDNS FQDN as the hostname and similarly its domain part for the domainname. There are entries above for the IP address that are made manually so these have to be checked periodically if changed by your broadband ISP. (This does not include the DDNS entry in the router which will update your DDNS service entry automatically). BZAG ======================================= --------------------------------------------------------------------- The official User-To-User support forum of the Apache HTTP Server Project. See <URL:http://httpd.apache.org/userslist.html> for more info. To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx " from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|