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/anti-abuse-wg@ripe.net/
[anti-abuse-wg] RIPE Database Proxy Service Issues
- Previous message (by thread): [anti-abuse-wg] RIPE Database Proxy Service Issues
- Next message (by thread): [anti-abuse-wg] RIPE Database Proxy Service Issues
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Kaveh Ranjbar
kranjbar at ripe.net
Wed Jan 2 23:11:09 CET 2013
On Jan 2, 2013, at 10:00 PM, Thor Kottelin <thor at anta.net> wrote: > > I'm not sure why you were blocked initially despite using the -r switch. I > was able to reproduce the problem: the IP address I used became blocked as > well. Perhaps this was some kind of overload protection rather than the > privacy-related restriction we have been discussing. Hello Thor, This should not happen, could you please kindly contact us through ripe-dbm at ripe.net and give us your client IP address so we can investigate the cause. You should not get blocked when using "-r" flag with a RESOURCE query and there should be no overload issue at all. Please note "-r" flag will turn off recursion for contact information after retrieving the objects that match a query. If the query is directly for personal data (like a person's name) using "-r' would have no effect as the direct query results will be objects with personal data. Kind Regards, Kaveh. --- Kaveh Ranjbar, RIPE NCC Database Group Manager
- Previous message (by thread): [anti-abuse-wg] RIPE Database Proxy Service Issues
- Next message (by thread): [anti-abuse-wg] RIPE Database Proxy Service Issues
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]