Joe Abley wrote on 2023-04-04 09:14:
> ... I think it's pretty common to talk about one nameserver for a zone being lame and another nameserver for the same zone not. Certainly that's not an uncommon configuration to find in the wild. I have always used "lame delegation" to refer to the situation where one nameserver in a delegation NS set (above the zone cut) not responding authoritatively for the QNAME that triggered the referral; that particular nameserver is lame for that particular zone. I think the response component is important since it speaks to how a nameserver is configured, which is important. ...
That's what the term "lame delegation" meant in BIND 4 back in 1989 or so when Mark Andrews, then at CSIRO, contributed the logic and the associated syslog() call. it wasn't popular since it told recursive server operators about authority configurations they could not fix.
It's kind of fun that there are so many ways that people think of this term when, in my experience, people generally agree enough when they are actually trying to debug something for the term to be useful.
a few years back somebody told me i named the RBL wrong and it's actually an acronym for something i didn't mean and don't agree with. "kind of fun" is now how i experienced that, but YMMV.
-- P Vixie _______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
