The Problem Being Addressed by this Proposal
In the DNS, a lame delegation is a DNS misconfiguration error. If a given DNS nameserver is designated as an authoritative server for a domain name, but does not return authoritative data for that name when queried, this is considered a lame delegation.
This could be due to the nameserver not having authoritative data for the DNS zone, or simply not responding at all.
DNS misconfigurations such as this have an operational impact on the global DNS as they cause additional unnecessary queries compared to having no delegations at all. However, the end result to a DNS client is ultimately the same: No data is found.
Also see:
- RFC1713, Section 2.3
- DNS Misconfiguration errors: Impact of Configuration Errors on DNS Robustness
- Lame delegation in the AFRINIC database: How lame are our reverse delegations?
A large number of the reverse DNS delegations from the AFRINIC database are misconfigured in this way.
Ref. Name: AFPUB-2017-DNS-001-DRAFT-02 |
Versions:2.0 Status: Pending Board Ratification Obsoletes: CPM 3.0 - The Policy Development (PDP) |
Author:
|
Submitted: 22 November 2017 |
Revision History
Date |
Details |
22 Nov 2017 |
Version 2.0 A complete rewrite of the text to simplify and clarify. Neither the intent, nor the actions and results of the proposal have changed. The text is simply now confined to a brief problem statement and the desired end result.
|
15 Mar 2017 |
Version 1.0 |