Hi Anurag,
37.111.192.0/18 was transferred from RIPE to Grameenphone at APNIC on 20 Feb 2017 (https://www.apnic.net/manage-ip/manage-resources/transfer-resources/transfer-logs/) Mac (FreeBSD) whois client is known to have issues with transferred resources and redirection between RIRs (https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=210892) You can also install a debian whois client to prevent the loop, but it will terminate with RIPE as the original resource holder, rather than APNIC as the final holder. There is no standard in providing a hint to whois clients that a resource has been transferred between RIRs. RDAP protocol solves this problem, and to some extent, special servers such as jwhois.apnic.net keep track of which RIR holds what space. Hope this helps, and happy to hear suggestions on how we could better track transferred resources in Whois. Regards, Sanjaya From: [email protected] <[email protected]> On Behalf Of Anurag Bhatia Sent: Friday, 26 April 2019 5:15 AM To: mailman_APNIC-talk <[email protected]> Subject: [apnic-talk] Question about 37.111.227.0/24 Hello everyone I am trying to understand what is special about 37.111.227.0/24<http://37.111.227.0/24>? It's being announced by Aamra Bangladesh (AS58601) and route object seems to be registered for Grameenphone Bangladesh. The strange behaviour I see for this is: 1. Mac whois query for this goes into an endlessly repeating loop. whois on Linux works fine. 2. Linux whois leads me to IANA but the query to jwhois.apnic.net<http://jwhois.apnic.net> leads to Grameenphone. Anyone with an idea of why whois isn't playing well? Is it a pool transferred across RIRs? If so, any good reading point about these problems? Thanks. -- Anurag Bhatia anuragbhatia.com<http://anuragbhatia.com>
_______________________________________________ apnic-talk mailing list [email protected] https://mailman.apnic.net/mailman/listinfo/apnic-talk
