BIND 9.11.9-1+ubuntu18.04.1+deb.sury.org+2 crash

[Ondřej Surý]

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,
Ondrej
--
Ondřej Surý
ondrej at isc.org

> On 25 Jul 2019, at 07:40, FUSTE Emmanuel <emmanuel.fuste at thalesgroup.com> wrote:
> 
> 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/issues with more details on you named.conf.
>> 
>> You can use named-checkconf -px to clean any sensitive data, and/or make sure you mark the
>> issue as confidential if there’s still data you don’t want to be seen by general public.  We’ll sanitize
>> the issue later.
>> 
>> That said - the 9.11.9-1+ubuntu18.04.1+deb.sury.org+2 backport has missed one important commit
>> that disables legacy GeoIP and enables GeoIP2, and I’ve just uploaded version 3+geoip2 to the
>> Ubuntu repositories, so could you please try again with the recompiled version?  It should fix the
>> INSIST() that you were hitting.
>> 
>> If that fixes your issue, we would still appreciate if you would create the issue, so we can make
>> BIND fail more gracefully that with an crash if there’s error in the configuration related to the
>> switch between GeoIP and GeoIP2.
>> 
>> Thank you,
>> Ondrej
>> --
>> Ondřej Surý
>> ondrej at isc.org
>> 
>> 
> Hello Ondrej,
> 
> Thank you for your quick reply.
> I will create the issue shortly.
> As explained in my followup message, it is now very difficult for me to 
> test the updated package. I will try to find a way to test/validate it 
> as time permit.
> 
> Thank you
> Emmanuel.