-----BEGIN PGP SIGNED MESSAGE----- Hash: RIPEMD160 On Mon, Jun 13, 2005 at 01:34:10 PM -0500, Kenny Hitt wrote: > Hi. > > Yes, it works with DHCP. My domain is on a box connected to a cable > modem. When my IP changes, it is easy to update it with dyndns.org. To elaborate on what Kenny saidd you can also use dyndns even if your server is behind a router/firewall. Just make sure that you have the necessary ports open such as 80 and 443 (if you use https) and that these ports are forwarded to the right machine on your network. This is often frustrating to set up with the routers because the router also uses dhcp to assign local addresses so you will want to set up some static mappings in the router so that the same hardware address always gets the same ip address. Once the outside world can get to your server you need to make sure it is correctly referred to in the dns. The client I use for this is ddclient which will update my dyndns.org account when my ip address changes. You have to be sure to tell ddclient to get your address from the web using an address like http://checkip.dyndns.org. This will ensure that you don't set up your domain name to point to a local (unroutable) address. I have probably made this whole process seem more complicated than it is, but looking at the ddclient(1) and ddclient.conf(5) man pages should help clear it up. > Hope this helps. Yeah, what he said. - -- "Debugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you are, by definition, not smart enough to debug it." - Brian W. Kernighan Thomas Stivers e-mail: stivers_t at tomass.dyndns.org -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFCrdfz5JK61UXLur0RA4MWAJ9eMmW0lMp3ajHJHmtUgcrVwXcbhwCggc2P YPjxLZC07HdzRXeHHgF4ScI= =5zw8 -----END PGP SIGNATURE-----
