This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/dns-wg@ripe.net/
[dns-wg] Progress with DNS Quality, Also: Lameness
- Previous message (by thread): [dns-wg] Progress with DNS Quality, Also: Lameness
- Next message (by thread): [dns-wg] Progress with DNS Quality, Also: Lameness
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Patrik Fältström
paf at cisco.com
Thu May 22 11:09:14 CEST 2003
On torsdag, maj 22, 2003, at 10:02 Europe/Stockholm, Daniel Karrenberg
wrote:
> Nothing changes really despite a lot of effort put in and
> a lot of improvement in the (self)policing tools.
To be honest, the result I have shows for .SE:
- Overall "errors" is 22.5%
- Errors "large" DNS operators have is approximately 1%
- "Large" DNS operators are asking me many questions because
they think 1% is too bad (they have pushed it down from 1.1% to 0.6%
So, my conclusion is that one can not look at the overall average
because I don't think that matters so much. Many domains being lame and
bad (in the forward zones) might be domain names only "registered" by
people wanting the domain name, but they are not "in use".
For in-addr.arpa, I don't know if one can draw the same or similar
conclusions. It might be more the ISP interest of running in-addr.arpa
in the first place which matters.
paf
- Previous message (by thread): [dns-wg] Progress with DNS Quality, Also: Lameness
- Next message (by thread): [dns-wg] Progress with DNS Quality, Also: Lameness
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ dns-wg Archives ]