-
Notifications
You must be signed in to change notification settings - Fork 68
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Does the Maxmind GeoLite Legacy Database Discontinuance affect gdnsd? #161
Comments
Thanks for bringing it up, I hadn't noticed this! For (1) yes, the answer is "use GeoLite2". For (2), it's a bit trickier! In code terms, I think we can handle this with at most some minor updates. I honestly haven't tested what the failure mode will be in that case (yet). The failure mode should be sane in the code sense (no crash), but I fear it could be "silent" (as in, loading up the new coordinate-free GeoLite2 City may just result in default/awful mapping of clients that used to map sanely, without much feedback to the administrator about what's going on). We'll probably want to find a way to make this user-friendlier and fail at city_auto_mode operation completely if the database is a coordinate-free "GeoLite2 City". Some documentation updates might be helpful as well. Beyond making sure the documentation is informative, and that the code fails in an acceptable way, there's not a whole lot we can do other than offer advice in the case of gdnsd deployers who have been relying on auto-mapping via the free GeoLite2 City data. As far as I can tell, there's no plan to drop coordinate data from the commercial GeoIP2 City databases, just the free GeoLite2 City databases.
|
Hi Brandon, thank you for your response to this. I have to admit I will have to chew on this a bit to figure out the impacts and logical next steps for my setup ... I have been using GeoLite, so I am going to have to do something with this ASAP.
Thank you |
All GeoIP2 databases will have some networks mapped to objects that do not contain coordinates (satellite, anon-proxy, and some unlabeled unknowns as well), and plugin map statements can overlay fixed and coordinate-based mapping to varying degrees, so there's not even a reliable measurement we could use like "X% of coordinate lookups must succeed" to try to figure this out precisely and automatically. So, while it would have been nicer to detect this based on the data, it's not realistic in terms of complexity, cost, or accuracy. Our only reasonable alternative here is to rely on the database's own metadata description abd build epoch times. Fixes #161 (cherry picked from commit 2415dab)
I was just reading this: https://support.maxmind.com/geolite-legacy-discontinuation-notice/
Thanks in advance for any insights.
The text was updated successfully, but these errors were encountered: