In message <[email protected]> Ted Lemon writes: > The problem of secondarying the reverse zone isn't really discussed in > the dns-pd draft, and there are a number of operational details I'd > like to flesh out, but the specific question of secondarying the > reverse zone isn't quite what it seems. > > You secondary a zone so that the contents of the zone will be there > when a query happens, but why would a query happen if the CPE device > isn't reachable? What would trigger that query? So I think you can > get away with _not_ secondarying the zone. But if you do want to > secondary it, why would the ISP be responsible for that? Presumably > the customer is pretty savvy; a secondary for their reverse tree would > just be another service they'd want to buy or set up, and the ISP > could wash their hands of it or sell it, whichever they chose.
Anything DNS related should be reliable. Therefore a secondary would be preferable to not having one. For example, someone looking at logs that store only IP address for performance reasons (this is common for http logs) would have only an IP address. Using the example in http://www.ietf.org/mail-archive/web/homenet/current/msg01286.html an email reporting a compromised host would have Mary-Perkins-Laptop" in the email rather than a:b:c:d::123 in the email. Yes. I agree that ISPs won't even give you the time of day without wanting to charge you for it. [Ever ask about NTP service? :)] That doesn't mean we shouldn't define protocols that support doing useful things, even if later an ISP may try to charge for it. There are a few places where you can still get a free DNS secondary. Definitely not at my ISP (not free or even for a fee). Curtis _______________________________________________ homenet mailing list [email protected] https://www.ietf.org/mailman/listinfo/homenet
