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/[email protected]/
[db-wg] Overly specific inet6num objects by Hetzner
- Previous message (by thread): [db-wg] Overly specific inet6num objects by Hetzner
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
denis walker
ripedenis at gmail.com
Sat Apr 27 23:30:53 CEST 2024
Hi On Sat, 27 Apr 2024 at 20:56, Semisol via db-wg <db-wg at ripe.net> wrote: > > Hetzner apparently creates an `inet6num` object per dedicated server allocation (enough to get my IP blocked for 1 day trying to query them all), and it took several seconds to execute the query. > > > whois -r -- "-i mnt-by HOS-GUN -T inet6num" The '-r' has to be part of the command you send to the whois server if you don't want all the personal data (which is why you were blocked). (see https://apps.db.ripe.net/docs/How-to-Query-the-RIPE-Database/Command-Line-Queries/#whois-client) Maybe try this query instead: whois -h whois.ripe.net -- "-r -i mnt-by HOS-GUN -T inet6num" cheers denis co-chair DB-WG > (warning: this will get your IP blocked) > > Some questions: > > Is there any policy about "too specific" objects? > Is there any plans to restrict how many objects a single query can get at once? > > -- > > To unsubscribe from this mailing list, get a password reminder, or change your subscription options, please visit: https://mailman.ripe.net/
- Previous message (by thread): [db-wg] Overly specific inet6num objects by Hetzner
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]