|
North American Network Operators Group Date Prev | Date Next | Date Index | Thread Index | Author Index | Historical Re: AW: Odd policy question.
On Sat, 14 Jan 2006 17:06:20 EST, "Jeffrey I. Schiller" said: > Foolish me. Indeed all that is required is a way to detect that the > delegation is lame (hopefully in a secure fashion) and remove the lame > delegations. Of course that does leave the problem of what to do if all > of the delegations are lame, as Randy has alluded to. If all the delegations are totally lame, then as a *practical* matter the domain is borked anyhow - the only information lost if you simply nuke the whole thing is the SOA (and several incorrect NS records). At one time, I would have suggested trying to contact the entity specified on the SOA. But these days, I'm tempted to say that if they can't get *one* NS pointing at something that will answer, they don't deserve a domain at all... (As noted, there *is* an interesting security exposure if an attacker can force an NS to be reported as lame. On the other hand, the current state of security at most DNS registrars seems to imply that the DNS domain holders don't really care about security anyhow.. ;) Attachment:
pgp00013.pgp
|