The issue was caused by using GeoIP2 configuration with BIND 9.11
compiled with legacy GeoIP, so there’s no need to test it on your side.
We are just missing the combination of the options that you have used
that caused this, thus the issue. We would be able to test it ourselves
then.
Thank you,
Le 25/07/2019 à 12:56, Ondřej Surý a écrit :
> Hi Emmanuel,
>
> the crash should not happen because the discrepancy between the GeoIP and
> GeoIP2 configurations
> should have been caught earlier, so I would appreciate if you can submit an
> issue here:
> https://gitlab.isc.org/isc-projects/bind9
Hi Emmanuel,
the crash should not happen because the discrepancy between the GeoIP and
GeoIP2 configurations
should have been caught earlier, so I would appreciate if you can submit an
issue here:
https://gitlab.isc.org/isc-projects/bind9/issues with more details on you
named.conf.
You can use
Ok, I installed GeoLite2 databases and adapted named.conf.options and
apparmor profile and my service is resumed.
It is the second time I'm forced to switch from an ESV version to the
lastest version because of a bad update.
Bugs is life, but do not pull previous version so quickly. I'm no longer
4 matches
Mail list logo
