DRAFT: Measuring and Reporting on Reverse Tree DNS Lameness in the RIPE NCC Service Region.
- This table includes those parts of Early Registration Transfer (ERX) space that are under the control of the RIPE NCC.
- ERX was a project to take IP allocations made before the RIR System started and move them into management by Regional Internet Registries.
The RIPE NCC provides DNS delegations within these zones for IP address ranges allocated to network operators. For further details see:
A survey carried out in March 2006 revealed that around 11-13% of the nameservers listed in the delegations are 'lame', meaning they are not responding correctly.
Definition of Lameness
There are several definitions of lameness available. However, within the context of this document and these checks, a server will be regarded as lame if it does not satisfy the following test:
If a server fails this test it will be retried five times over a period of ten days (at varying times of day). After this time, it will be classed as lame.
Lameness Checking and Reporting
The RIPE NCC will run a lameness check once each month against all DNS servers listed as delegation points within the RIPE NCC delegated zones.
Interaction with ns.ripe.net
The sample text of the alert email that we will send to operators with servers reported as lame:
Dear administrator of [server name]
According to checks made on [date], your server, [server name],
was lame for the following zone(s):
For information about the checks that we made on your zone(s), please see: