esr@xxxxxxxxxxx (Eric S. Raymond) wrote on 22.11.04 in <20041122194938.GA9185@xxxxxxxxxxx>: > 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. > > 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. It doesn't? Then pray, what is it I use at the job that does exactly this? (Hint: ISC DHCP 3 & ISC BIND 9, running on a Debian woody/sarge hybrid install.) Oh, sorry. Not *exactly*. It's the DHCP *server* which does the DNS update. > I don't think my situation is unique. It's at least rather strange. MfG Kai _______________________________________________ Ietf@xxxxxxxx https://www1.ietf.org/mailman/listinfo/ietf