On Mon, 2004-11-22 at 14:49 -0500, Eric S. Raymond wrote: > Fred Baker <fred@xxxxxxxxx>: > > I submit that if your environment is at all like mine, you don't actually > > configure 192.168.whatever addresses on the equipment in your house. You > > run DHCP within the home and it assigns such. That being the case, you > > actually don't know or care what the addresses are on your equipment. You > > care that your SIP Proxy and etc know the relationships, and they derive > > them directly without your intervention. > > Actually, I do set up static addresses. I'd use DHCP, but if I did that > I would not be able to refer to the machines on my local net by name. I do hope that you know you can assign 'static' addresses based on MAC address and a number of other properties that the dhcp client provides. The dhcp server will then just assign the configured prefix. This is actually what most ISP's use, but they will only give people one IP. > Until my DHCP client can update my DNS tables with name information > on the fly, I'll keep doing doing it this way. Apple's zeroconf > technology solves this problem, albeit in a slightly different way, > but Linux doesn't deploy it yet. Even Windows can do that ;) But so can any UNIX or basically anything where you can compile bind utils on: http://ops.ietf.org/dns/dynupd/secure-ddns-howto.html or the exact same thing but for Windows: http://unfix.org/~jeroen/archive/Windows_DynamicDNS_Update.zip Greets, Jeroen
Attachment:
signature.asc
Description: This is a digitally signed message part
_______________________________________________ Ietf@xxxxxxxx https://www1.ietf.org/mailman/listinfo/ietf