[dns-resolver-tf] Final draft of RIPE DNS Resolver Best Common Practices
- Previous message (by thread): [dns-resolver-tf] Final draft of RIPE DNS Resolver Best Common Practices
- Next message (by thread): [dns-resolver-tf] Final draft of RIPE DNS Resolver Best Common Practices
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Mirjam Kuehne
mir at zu-hause.nl
Mon Mar 18 09:59:54 CET 2024
Many thanks for putting this together, Shane and thanks to all of you for contributing to this document! I am looking forward to seeing this published as a RIPE Document so it can become a useful source of knowledge for DNS resolver operators. Kind regards, Mirjam On 17/03/2024 17:09, Shane Kerr wrote: > Fellow Task Force members, > > I have updated the document based on the feedback and text from Farzaneh > and John. > > If you spot anything at this point, please let me know. I plan on > turning the document over to the RIPE NCC for editing on 2024-03-29 (29 > March 2024). I know that it is not perfect, but I'd like to get it > published at some point. 😉 > > I included all changes except for the cache flushing suggestion: > > * Added description of the problems with ANY replies. > > * Added a section about name server identification. > > * Added the proposal to document as much about blocklists as possible, > even if source of the blocklists themselves cannot be published. > > * Added a section about NTA transparency. > > Again, thank you all for the work you've put in. > > Cheers, > > -- > Shane > > [..]
- Previous message (by thread): [dns-resolver-tf] Final draft of RIPE DNS Resolver Best Common Practices
- Next message (by thread): [dns-resolver-tf] Final draft of RIPE DNS Resolver Best Common Practices
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]