Thank you for all the feedback, it is very interesting.
But I’m not looking at the IP addresses hitting my server, I’m going according to my monitor page: pool.ntp.org: Statistics for 160.119.230.39
If the client is in US, but uses a privacy DNS server in, say, Africa, then that would still, from the point of view of the stats, look like a client from Africa, would it not?
And if MaxMind is used in the stats and the DNS server finding closest IPs, then incorrect MaxMind data would also “balance out” and, even if the client is in US but MaxMind thinks he is in Africa, he would get an IP in Africa, but he would also be reported as an African client?
Ok, so my bandwidth is set at 3Gbit. And I’m part of @. When does a client get assigned an IP outside their zone when they do have a server in their zone?
The only thing I could come up with is that should a continent zone also not have any servers in it, the fallback would then be to the global “@” zone.
But the US itself has many servers, so this also does not work?
I’m just trying to match this up with the issue Bas is having(had?) problems with an overloaded zone. In his first post( I take a big hit in queries ) his server is 36X overloaded in his own zone, and US is also 3’rd in his clients?