Something strange with RIPE DB
Hello! I have a strange behaviour of RIPE DB right now: whois-request from IP 193.0.227.234 returns: # whois -r АS43668 % This is the RIPE Database query service. % The objects are in RPSL format. % % The RIPE Database is subject to Terms and Conditions. % See http://www.ripe.net/db/support/db-terms-conditions.pdf %ERROR:101: no entries found % % No entries found in source RIPE. % This query was served by the RIPE Database Query Service version 1.19.5 (WHOIS3) The same request from 109.68.46.146 returns normal output. Did anyone experience similar problem? -- Alexander Shikov IT Consulting L.L.C. Tel.: +380 44 201 1407 | Fax: +380 44 201 1409 | Mob.: +380 50 410 3057
You are likely blacklisted, query works fine for me also from Ukrainian 193.* PI space (Routed at Ukrtelecom) -- William Weber | RIPE: WW | LIR: at.edisgmbh william@edisglobal.com | william@edis.at | http://edis.at | http://as57169.net EDIS GmbH (AS57169) NOC Graz, Austria Am 05.08.2012 um 21:51 schrieb Alexander Shikov <a.shikov@itcons.net.ua>:
193.0.227.234
On Sun, Aug 05, 2012 at 10:18:31PM +0200, William Weber wrote:
You are likely blacklisted, query works fine for me also from Ukrainian 193.* PI space (Routed at Ukrtelecom)
I don't think I'm blacklisted. It seems that there is (or was) a problem with whois service. Two identical requests from 193.0.227.234, but replies are different: # whois -r AS43668 % This is the RIPE Database query service. % The objects are in RPSL format. % % The RIPE Database is subject to Terms and Conditions. % See http://www.ripe.net/db/support/db-terms-conditions.pdf % Note: this output has been filtered. % To receive output for a database update, use the "-B" flag. % Information related to 'AS43008 - AS44031' as-block: AS43008 - AS44031 [...] % This query was served by the RIPE Database Query Service version 1.19.5 (WHOIS2) # % This is the RIPE Database query service. % The objects are in RPSL format. % % The RIPE Database is subject to Terms and Conditions. % See http://www.ripe.net/db/support/db-terms-conditions.pdf %ERROR:101: no entries found % % No entries found in source RIPE. % This query was served by the RIPE Database Query Service version 1.19.5 (WHOIS4) And right now the problem has dissapeared. -- Alexander Shikov IT Consulting L.L.C. Tel.: +380 44 201 1407 | Fax: +380 44 201 1409 | Mob.: +380 50 410 3057
Dear Alexander, Thank you for your report. You are right about not being blocked, in case of an access restriction, the error message clearly states the cause. We have investigated the query you have mentioned throughly. In cases of no results, what we have received at our side was the word "АS43668" with the letter A written in Cyrillic Capital Letter А. That is U+0410 instead of U+0041 which was also used in the original email in this thread as well and this results in no objects found. We will shortly add a feature to append a comment to the output whenever non-ascii characters are supplied in the query string. If this should happen again, it will be clear to the client that these characters have been used. Kind Regards, Kaveh. --- Kaveh Ranjbar, RIPE NCC Database Group Manager On Aug 5, 2012, at 11:28 PM, Alexander Shikov <a.shikov@itcons.net.ua> wrote:
On Sun, Aug 05, 2012 at 10:18:31PM +0200, William Weber wrote:
You are likely blacklisted, query works fine for me also from Ukrainian 193.* PI space (Routed at Ukrtelecom)
I don't think I'm blacklisted. It seems that there is (or was) a problem with whois service. Two identical requests from 193.0.227.234, but replies are different: ...
participants (3)
-
Alexander Shikov -
Kaveh Ranjbar -
William Weber