ripe policy about reverse dns?
Hello, I tend to remember that RIPE had a strict policy about delegated address space reverse DNS: adresses must have a valid reverse and delegated (sub) blocks must be registered in RIPE db. I wanted to refer to the document mentioning these requirements but I was not able to find them. Navigating on www.ripe.net helped nothing: reverse dns part shows the procedure, refers to a page "about ripe policies" which contains only links to RFC and other RIPE documents, which in turn are about the procedure and not any policy. Maybe there are any hidden one mentioning that "you should have reverse on your addresses" but I kindly ask your help where to look for it. If this requirement would have been dropped then I'd be extremely happy to know about it. Thank you, Peter ps: Reason is a(nother) big provider with many /19 and with no reverse or RIPE entry (other than the /19) whatsoever, and occasional spam from these reverseless and nameless blocks.
Peter Gervai <grin@grin.hu> wrote:
I tend to remember that RIPE had a strict policy about delegated address space reverse DNS: adresses must have a valid reverse and delegated (sub) blocks must be registered in RIPE db. I wanted to refer to the document mentioning these requirements but I was not able to find them.
Hello Peter, The reverse delegation policy is documented in: http://www.ripe.net/ripe/docs/rev-del.html There is _no_ wording about the RIPE NCC requiring reverse delegation to be set up by the LIR or by the end users. I reckon that the language you tend to remember is from the RIPE 244 (obsoleted) section 5.0: "LIRs should provide reverse delegation corresponding to an assignment during the complete validity period of the assignment." I hope this answers your query. Kind regards, -- Olaf Kolkman RIPE NCC. PS. "Encouraging the use of DNS IN-ADDR Mapping" by D. Senie might be relevant. That draft is currently discussed in the IETF DNSOP working group, the most recent revision can be found at: http://www.senie.com/dan/draft-ietf-dnsop-inaddr-required.txt ---------------------------------| Olaf M. Kolkman ---------------------------------| RIPE NCC
participants (2)
-
Olaf M. Kolkman -
Peter Gervai