This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/[email protected]/
[dns-wg] Solving lameness in the reverse zones
- Previous message (by thread): [dns-wg] Solving lameness in the reverse zones
- Next message (by thread): [dns-wg] RIPE 59 minutes
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Shane Kerr
shane at time-travellers.org
Fri Oct 23 12:14:51 CEST 2009
Wilfried, On Fri, 2009-10-23 at 08:44 +0000, Wilfried Woeber, UniVie/ACOnet wrote: > Shane Kerr wrote: > > > All, > > > > DNS Lameness Philosophy > > ----------------------- > > There are two fundamentally different philosophies about lameness in > > reverse DNS. > > Well, my perception is that reverseDNS is not well-understood by a big > portion of all the players involved. > > On top of that, the built-in redundancy and resilience of DNS tend to > hide structural problems from the "consumers" till the very last moment. In my mind, this means that there is no problem, and that most attempts to solve the non-existent problem are doomed to be more expensive than the benefit they bring. I think my lightweight proposal (include lameness in an annual report about the state of delegations per LIR, notify the top offenders) is the right way forward. It should provide the most benefit for the least annoyance. -- Shane
- Previous message (by thread): [dns-wg] Solving lameness in the reverse zones
- Next message (by thread): [dns-wg] RIPE 59 minutes
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ dns-wg Archives ]