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]/
[anti-abuse-wg] whois access
- Previous message (by thread): [anti-abuse-wg] whois access
- Next message (by thread): [anti-abuse-wg] whois access
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Niall Donegan
niall at blacknight.com
Thu Dec 15 18:16:42 CET 2011
On 15/12/11 16:42, russ at consumer.net wrote: > As for passing through the IP of the requesters of the whois records I > have asked about this several times. ARIN told me they don't support > it and RIPE won't answer my inquiries. Are there standards for that > or any other information about setting up some sort of ip address > pass-through or proxy for whois queries for the RIR's? That's because whois is one of the simplest protocols there is. For example, to get the details for 192.0.2.1, just telnet into port 43 of whois.ripe.net. As soon as the disclaimer comes up, type "192.0.2.1" followed by enter, and you get the results. Why would you want to mess up as simple a protocol as that with something like the X-Forwarded-For header in HTTP? RIPE can only see the IP you're connecting from, and it's doing a lot more traffic than a normal IP. If you have a legit need, they can and will give you bulk access for that ip. Niall. -- Niall Donegan ---------------- http://www.blacknight.com Blacknight Internet Solutions Ltd, Unit 12A, Barrowside Business Park, Sleaty Road, Graiguecullen, Carlow, Ireland Company No.: 370845
- Previous message (by thread): [anti-abuse-wg] whois access
- Next message (by thread): [anti-abuse-wg] whois access
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]