On Tue, Sep 11, 2012 at 12:37:30PM -0400, Ted Lemon wrote: > No. Things change. All that's required to deal with this is that the > underlying protocol support it. The DHCP DUID identification system > does support this kind of change, as long as the actual device doesn't > change. If the device changes, then when the registration expires, the > name can be reclaimed.
This does raise a point, though: Dynamic DNS doesn't have an expiration mechanism. Populating the DNS using mDNS is a good idea, I think, but it might be nice if we had some method of signaling the intended future disposation of a name. I'm thinking along the lines of a new rrtype, or maybe just a TXT record, that can indicate things like "after time T, it's okay to delete this rrset", or "if this name already exists with a different address, it's okay to replace the old one instead of adding to it". My home zone is cluttered up with the names of a couple of dozen laptops and ipods belonging to neighbors and visitors over the past year. It's probably my own fault for misconfiguring DHCP (I don't think it's doing the right thing in the "on expiry" block, and it hasn't been a high priority for me to fix it). But if we're going to be supplying DNS data from multiple sources -- DHCP, mDNS, maybe others -- then it might be a good idea to manage time limits on the demand side. -- Evan Hunt -- e...@isc.org Internet Systems Consortium, Inc. _______________________________________________ homenet mailing list homenet@ietf.org https://www.ietf.org/mailman/listinfo/homenet
