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] Whois referrals changed source IP
- Previous message (by thread): [db-wg] Alex Dempsey/Vodafone is out of the office.
- Next message (by thread): [db-wg] Whois referrals changed source IP
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Robert Martin-Legene
robert at dk-hostmaster.dk
Thu Nov 18 12:51:28 CET 2004
For those of you (TLD's only?) who receives whois referrals from whois.ripe.net and thought they would always come from 193.0.0.0/24, it now seems that even though whois.ripe.net is in that range, the referrals can come from at least 193.0.4.152 (as it does right now). For us, we only allow the -V3.2.0,$IP option (stating the origin IP) if from an "NCC IP#". For all other IP## using that option we would give an error. Our last request from 193.0.0.0/24 was received Nov 17 11:16:46. Would the NCC be kind enough to officially inform of which range(s) the requests can come from? (I doubt it's the entire 193.0.0.0/21, which are server networks.) (And to think that it was actually Verisign who mailed us to let us know they had a problem using our whois server, I find kind of funny). -- Robert Martin-Legène IT security manager DK Hostmaster A/S
- Previous message (by thread): [db-wg] Alex Dempsey/Vodafone is out of the office.
- Next message (by thread): [db-wg] Whois referrals changed source IP
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]