[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] Solving lameness in the reverse zones
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Matus UHLAR - fantomas
uhlar at fantomas.sk
Fri Oct 23 13:57:43 CEST 2009
> On Thu, 2009-10-22 at 17:22 -0500, Michael Graff wrote: > > Are lame delegations really such a problem that we need to take drastic > > action? How often would this be checked, and how much liability would > > be here in modifying what is published? I'd hate to see the papers when > > a large content provider lost due to a temporary outage on one name > > server... On 23.10.09 12:11, Shane Kerr wrote: > This approach is based on the assumption that lameness is in itself a > problem, and must be fixed. > > Also note that we are talking about the reverse DNS in this case, so > nobody is going to lose revenue if we a delegation is removed. well, there are still servers and services requiring reverse resolution... -- Matus UHLAR - fantomas, uhlar at fantomas.sk ; http://www.fantomas.sk/ Warning: I wish NOT to receive e-mail advertising to this address. Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu. REALITY.SYS corrupted. Press any key to reboot Universe.
- Previous message (by thread): [dns-wg] Solving lameness in the reverse zones
- Next message (by thread): [dns-wg] Solving lameness in the reverse zones
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ dns-wg Archives ]