>>213 I have not turned host name lookups on. And no change to configuration. However burbon system sounds very nice, but might be a duplicate of something we already have. Good morning Everyone.
>>214 This concerns me. 1) config changed on bbspink www server, something not "inverted-ip-address.niku.2ch.net" started to come into BBQ. I did not change any configurations.
The difference between pasegueno and burbon system is burbon system is for valid for blocking too many threads creation, too many postings, and too many reading requests (crawling) to a server in a short period time(using ● or not), thus helps to decrease server overloads and works as a tool against vandals as a side effect.
<Another speculation> I think Jim-san may added a tool to modify .htaccess for doing "deny from [host name]" to the bbspink side servers instead of changing httpd.conf value.
When Apache process [deny from host name] in a .htaccess list, it does reverse DNS lookups for ALL accesses in order to match the list. even if HostNameLookups in httpd.conf was off.
2ch servers were not made such a way, since reverse DNS lookups of all accesses results severe performance penalty. 2ch handles and writes tools for "deny from [IP address]" only in the past and won't change it in a future. <Speculation end>
>>219 Yes, I understand. pasegueno is not set to stop reading requests, although that is possible. Lets use burbon system for that. Pasegueno is currently set to only stop to many writing requests. >>220 Yes please cool down...:) We have been using both ip and dns on the .htaccess for over one year now. Is it a recent event that has caused this problem? Or it could be an error or mistake by me. I make mistakes all of the time.
>>221 The trouble happened just after >>191-193, but as >>215 says, the poisoning of main reload(reading) burbon IP list with host names instead of IP address was the cause. The poisoning may have gone slow and did not cause fatal error until now if pink servers were using host names for about a year now.
>>224 Hi Jim-san. What root-san is concerned about are hostnames on files for reload-bourbon, which are collected by f22base server. He says malformed file force-enabled reverse DNS lookups on all of 2ch servers, and caused malfunction in reload- bourbon, In http://qb5.2ch.net/test/read.cgi/operate/1223317539/585-595 . he mentioned that reload-bourbon will be configured to drop anything other than IPv4 and v6 address, implying 2ch isn't negative to switch to v6. Also mentioned is that reload-bourbon system has now disconnected from pink to prevent further problems. I think I've seen root-san post in English. Maybe you can talk to him directly on this issue.
>>224 ipv6...hmm...ipv6.2ch.net is around for about a year for testing purpose. But it seems that it is not popular among users. Very little ISP supports ipv6 in Japan and will take years for typical consumers to use it in common.
If ipv6 <-> ipv4 address conversion can be done without performance penalty and has proven reliabity, it might be worth checking for them. In my opinion, 2ch is very conservative as far as network is concerned though.
>>226 I think I caused that manually. I accidently broke the file I was editing it to test when my internet connection failed. I thought it would overwrite again in a few minutes and fix it. I am the vandal...orz
>>228 One more opinion, if you would like to put the burbon system back to bbspink server: There must be a file that contains ip address list to pass it to burbon system when F22(burbon main server) requests it every 10 minutes. If you are going to fix something, please make sure that the file does not include any host names in it. If you have no idea which one is the correct file, it is a better idea to ask for it to root-san.