recently added an IPv6 NTP server to the pool (2001:470:b80f:28::15) which was auto-assigned to the europe and fr zones, but the server is physically located in the US (Texas). The incorrect geolocation is caused by Hurricane Electric’s tunnel broker — the routed /48 prefix (2001:470:b80f::/48) geolocates to France/Europe in IP databases, but the actual server is in North Texas (Vexus Fiber, AS40676 area).
The correct zones should be north-america and us, matching my IPv4 entry (38.28.93.135) which is correctly assigned.
Is there a way to manually correct the zone assignment for this server?
Hi @StrawberryMew,
Send an e-mail to server-owner-help@ntppool.org, but be prepared that it may take a while, or that you may have to resend your request after a while.
Or you could try making the change at the source, and then re-add your server once the change has propagated to the Pool system (if a change is accepted, it will appear in one of the two releases MaxMind make per week, and the Pool DNS servers reload the data twice a week as well). Or simply wait to see whether they update on their own, as HE seems to have set up a geofeed to MaxMind to put the server in the country of the HE account holder (my servers regularly get placed in my country of residence, regardless of where the server or tunnel endpoint is actually located).
As it’s sometimes a bit unpredictable as to when Pool staff get around to adressing your change request, I’d try both paths in parallel if you’re in a hurry.
1 Like
Forgot: The comment field while registering the server could also be used to report misplaced servers - that’s actually one of its main use cases 
Same caveats as with the e-mail currently apply, though (both end up in the same ticketsystem).
And if it’s an option in your case: The tunnel subnet has a higher chance of being geolocated in the USA by default (and it’s sometimes difficult to convince MaxMind if the HE tunnel endpoint is located elsewhere).