RobiBue Posted February 24, 2019 Share Posted February 24, 2019 (edited) Cache refresh disabled to avoid rate-limiting of whois servers [refresh cache] $ whois NET-3-128-0-0-1@whois.arin.net [whois.arin.net] ERROR 503: Unable to service request due to high volume. hmmm interesting.... in the end, although it would go to /dev/nul for amazonaws, it can't find an owner now... No reporting addresses found for 3.208.7.29, using devnull for tracking. Edited February 24, 2019 by RobiBue Quote Link to comment Share on other sites More sharing options...
gnarlymarley Posted February 26, 2019 Share Posted February 26, 2019 Yeah, I am not sure if there is someone that has the ability to fix these cache entries. It is a tragedy now that we are here, but at the same time it is at least populating the blacklist. Display data: "whois 185.79.243.137@whois.arin.net" (Getting contact from whois.arin.net ) Redirect to ripe Display data: "whois 185.79.243.137@whois.ripe.net" (Getting contact from whois.ripe.net) whois.ripe.net 185.79.243.137 (nothing found) [whois.ripe.net] %ERROR:201: access denied for 184.94.240.92 Quote Link to comment Share on other sites More sharing options...
RobiBue Posted February 26, 2019 Author Share Posted February 26, 2019 (edited) 5 hours ago, gnarlymarley said: Yeah, I am not sure if there is someone that has the ability to fix these cache entries. It is a tragedy now that we are here, but at the same time it is at least populating the blacklist. Display data: "whois 185.79.243.137@whois.arin.net" (Getting contact from whois.arin.net ) Redirect to ripe Display data: "whois 185.79.243.137@whois.ripe.net" (Getting contact from whois.ripe.net) whois.ripe.net 185.79.243.137 (nothing found) [whois.ripe.net] %ERROR:201: access denied for 184.94.240.92 Oooh! This last part means that RIPE is blocking ironport/SpamCop/Cisco from accessing their Whois database... now that’s bad. Edited February 26, 2019 by RobiBue Quote Link to comment Share on other sites More sharing options...
gnarlymarley Posted March 2, 2019 Share Posted March 2, 2019 I just checked both yours and mine and they come back. I am not sure how long it takes for the cached whois to expire. Seeing the owner, I am not surprised about the /dev/null. [refresh cache] $ whois NET-3-128-0-0-1@whois.arin.net [whois.arin.net] . . . . NetRange: 3.128.0.0 - 3.255.255.255 CIDR: 3.128.0.0/9 NetName: AT-88-Z . . . . OrgAbuseEmail: abuse@amazonaws.com [refresh cache] $ whois 185.79.243.137@whois.ripe.net [whois.ripe.net] . . . . inetnum: 185.79.240.0 - 185.79.243.255 netname: PL-INTER-SAT-20141203 country: PL org: ORG-PTAO1-RIPE admin-c: JO3356-RIPE . . . . abuse-mailbox: jacek@inter-sat.pl Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.