it makes sense for ZW to prioritise ZW then fall back to ZA and then to other alternates yes
thanks Ralph Kind regards, Anthony Somerset
Somerset Technical Solutions Ltd. www.somersettechsolutions.co.uk Registered in the UK – Company no. 07738444 VAT Registration No: 140 6916 22 T: +44 (0) 33 0088 2751 E: anthony@somersettechsolutions.co.uk PGP: 0x7C892BF5
On 13 Feb 2014, at 23:11, Ralph Angenendt ralph.angenendt@gmail.com wrote:
Signed PGP part On 05.02.2014 09:21, Anthony Somerset wrote:
Hi Mirror team, any update on the following?
I'm seeing some bizzare mirror list results for ZW ip's right now - in fact we have never ever been offered the ZW mirror on any tested ZW IP!
from my home IP: http://f.sts.io/ssWvDoKRJD.txt - Mosty US servers?
from a ZW server: http://f.sts.io/u67AWSDCNt.txt - mix of global servers plus some SA (i kind of expect this but the ZW listing should be included as well)
very occasionally i get a listing like this: http://f.sts.io/0KseCzRxT9.txt - what appears to be a load of msync nodes?
is GeoIP needing an update or kick perhaps - is there any extra info we can provide you that would help to improve accuracy?
It is what I expected.
geo_cc.pm has
ZW => "ZA",
and ZA is:
za => 'il-br-tr-es-in'
Which means it is pure luck if your server is hit directly from ZW.
What I can do: Point ZW to itself (ZW => "ZW",) and than add
zw => 'zw-za-...' (whatever you think appropriate).
Cheers,
Ralph
CentOS-mirror mailing list CentOS-mirror@centos.org http://lists.centos.org/mailman/listinfo/centos-mirror