-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Rodolfo J. Paiz wrote:
>1. My notebook is assigned 192.168.0.102 by DHCP. >2. The DHCP server notifies DNS that "notebook IN A 192.168.0.102". >3. "ping notebook" does the right thing. >4. I reboot, get assigned .103 by DHCP. >5. DNS (and its cache) is updated. >6. "ping notebook" again does the right thing. Ok, so instead of having a pool like this: 192.168.1.11 d1-11.spotnet.org 192.168.1.12 d1-12.spotnet.org 192.168.1.13 d1-13.spotnet.org , when a machine whose DHCP_HOSTNAME is caspar is assigned 192.168.1.11, DNS gets changed so that 192.168.1.11 resolves to caspar.spotnet.org. Well, ok, but this is only going to work in very limited circumstances - -- i.e., a small, private network where you alone control DNS caching, which you say is the case for you, in which case, what's so hard about static assignments, or MAC-keyed DHCP leases? Further, if you need to reach the machine, then it qualifies as a resource server, and should (in my opinion) have a static IP anyway. And finally, on a public network, this is only approaches practicality if you set astonishingly low TTLs on those records. So I guess it all just sounds kludgy to me, but if it works for you ... - -d - -- David Talkington PGP key: http://www.prairienet.org/~dtalk/0xCA4C11AD.pgp -----BEGIN PGP SIGNATURE----- Version: PGP 6.5.8 Comment: Made with pgp4pine 1.75-6 iQA/AwUBPLONpb9BpdPKTBGtEQKSLgCgojTKRJSuHltrIoH/8r27+bT8dNMAoKbK EqvnqBgK8vzbctb+ufjXkiBg =NXl1 -----END PGP SIGNATURE----- _______________________________________________ Redhat-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-list
