Hello Piotr, Thanks for reply! You are absolutely right! I was using first resource to verify my changes. So as I understood my current DB information is OK from RIPE's point of view and the tool is not processing it correctly. And from the rest of Your message I understood that it wise to duplicate abuse contact in org: object as abuse-mailbox: attribute until everything will settle down right? Thanks! -- Best regards Levon Avagyan Core network engineer Ucom LLC On Thursday 13 February 2014 13:37:23 Piotr Strzyzewski wrote:
On Thu, Feb 13, 2014 at 01:46:20PM +0400, Levon Avagyan wrote:
Dear Levon
I need some help with proper setup of RIPE DB. I am currently updating our records and noticed that if i am adding ROLE abuse-c: "UCAB101-RIPE" with abuse-mailbox: "abuse@ucom.am" attribute to our org :"ORG-UL31-RIPE" object, it is not showing up in "Abuse Contact Finder" tool in Ripe Stat. It shows me message: "No contact information found for 44395" While if i am adding abuse-mailbox: attribute to org: object directly, it finds abuse contact just fine, however gives us 4/5 stars.
Is it a known bug or am i doing something wrong?
Thanks in advance.
P.S. Query: "whois as44395" returns abuse contact just fine.
Short answer: Don't use it. ;)
I assume that the tool you are using is this one: https://stat.ripe.net/special/abuse
The correct one is this one: http://apps.db.ripe.net/search/abuse-finder.html
However, the first one (from Ripe Stat) is still widely used due the fact that abuse-c is not fully deployed yet. Among others, the notable Abusix.org claims to use it.
If I understand https://labs.ripe.net/Members/Paul_P_/content-abuse-finder correctly, this tool doesn't look at aut-num at all. Please corect me if I'm wrong.
Moreover, this tool is full of false positives, no matter of how many stars it will show at the end. For example - it was just two weeks ago when I have deliberately created the situation that for not mine and not maintained by me inetnum I have forced this tool to claim with 4/5 stars that abuse@example.net is the contact information. Right now this is impossible, since I have notified about this the RIPE NCC and this tool is filtering the RFC-2606 dummy addresses out. Unfortunately, this was just one of examples.
Best regards, Piotr