On Wed, May 2, 2018 at 11:47 PM, Edward Lewis <edward.le...@icann.org>
wrote:
>
>
> If I can't find the text soon, I'll try to recreate the list of references
> at least.
>
We are in process of implementing a "Lame delegations" policy at AFRINIC
<http://tiny.cc/afrinic-lame>

We consider "lame" any NS which is either:
- Not responding at all.
- Responding in some way, but not for the specific domain queried.
- Responding for the correct domain, but without the authority bit set.

We used the definition in RFC1713:

A lame delegation is a serious error in DNS configurations, yet a
   (too) common one.  It happens when a name server is listed in the NS
   records for some domain and in fact it is not a server for that
   domain.  Queries are thus sent to the wrong servers, who don't know
   nothing (at least not as expected) about the queried domain.
   Furthermore, sometimes these hosts (if they exist!) don't even run
   name servers.  As a result, queries are timed out and resent, only to
   fail, thus creating (more) unnecessary traffic.


Cheers,
Amreesh
_______________________________________________
DNSOP mailing list
DNSOP@ietf.org
https://www.ietf.org/mailman/listinfo/dnsop

Reply via email to