With “balance out” I meant that if the DNS software uses maxmind, and thinks that the client is in zone CI, and the stats software uses maxmind then the stat software will also think that the client is in zone CI, so he will show in the stats as zone CI, even if he was in zone US all along. What I tried to say in a long-winded way was that maxmind should not be causing this miss-allocation. Don’t get me wrong, it probably does a lot of miss-allocation, but the stats should then also miss-allocate that client.
No, Bas was not complaining about the foreign traffic at all, I,m just using him as another example of high foreign traffic. This just struck me as interesting from his thread:
Same zone only. Even if global pool is used.
According to the stats page, the served zones are sorted according to the absolute number of queries, so I’m serving a small percentage of the total US queries, but in actual request number of queries it is still more than some of the actual request numbers for zones in my own continent.
So the only conclusion I can come to is that there are users in the US that use the africa.pool.ntp.org pool. Don’t know why though… People that moved from Africa to the US and never updated their device’s pool settings?
But I don’t think there is an answer to this questions.