Looking for users currently using “ip.renfei.net” — IP addresses “47.101.152.48” and “117.132.197.29”. There’s a problem with your program: starting March 31, 5 requests per second, 300 per minute, consuming a lot of public resources for two months now. Stopped on May 3–May 4, then started requesting fast again on May 5. This service is for pairing with DDNS; querying 5 times per second is completely unnecessary. Please modify your program to slow down the query requests. In April there were 320,000 requests; by the time of writing in May there have already been 4.2 million requests — a huge waste of public resources!!
“117.132.197.29” should be a China Mobile base station in Guangdong, then the program migrated to “47.101.152.48”, an Alibaba Cloud node in Shanghai. After moving to the cloud, the request rate rose from 200 per minute to 300 per minute. Since it’s now on the cloud, please comment out this piece of code. Your query logic is very likely an infinite loop constantly accessing.
What the “ip.renfei.net” Service Does
Use 1: Pairs with DDNS dynamic DNS resolution for resolving dynamic IPs. In a dynamic-IP environment, it conveniently updates domain resolution records in time. But domain registrars’ TTL minimums are generally 60 seconds, so querying once a minute is fastest enough; even querying the local IP every few minutes does nothing useful — fast querying has no effect.
Use 2: On Linux, use curl ip.renfei.net to quickly query the public outbound IP.
Use 3: In a browser, use JavaScript to request ip.renfei.net to get the user’s public IP address.
Abuse Wastes Public Resources
To keep the service stable and healthy, so you and others can use it stably, please don’t abuse public resources! “ip.renfei.net” has no CDN and no rate-limiting logic, to respond quickly. If lots of people write infinite loops to request it, performance is seriously affected, and I’ll have to add rate-limiting logic — but that will surely hurt the experience.