Join GitHub today
Does the Maxmind GeoLite Legacy Database Discontinuance affect gdnsd? #161
I was just reading this: https://support.maxmind.com/geolite-legacy-discontinuation-notice/
Thanks in advance for any insights.
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.