2
0
mirror of https://gitlab.isc.org/isc-projects/bind9 synced 2025-08-22 10:10:06 +00:00

add CHANGES note; remove references to legacy GeoIP from documentation

This commit is contained in:
Evan Hunt 2019-06-27 21:11:45 -07:00
parent 787f2a7e03
commit 55cca87d8a
5 changed files with 16 additions and 21 deletions

View File

@ -1,3 +1,5 @@
5262. [func] Removed support for the legacy GeoIP API. [GL #1112]
5261. [cleanup] Remove SO_BSDCOMPAT socket option usage. 5261. [cleanup] Remove SO_BSDCOMPAT socket option usage.
5260. [bug] dnstap-read was producing malformed output for large 5260. [bug] dnstap-read was producing malformed output for large
@ -10,9 +12,6 @@
will be compiled in by default if the "libmaxminddb" will be compiled in by default if the "libmaxminddb"
library is found at compile time, but can be library is found at compile time, but can be
suppressed using "configure --without-geoip2". suppressed using "configure --without-geoip2".
The legacy GeoIP API can be enabled by using
"configure --with-geoip". This cannot be used
together with GeoIP2.
Certain geoip ACL settings that were available with Certain geoip ACL settings that were available with
legacy GeoIP are not available when using GeoIP2. legacy GeoIP are not available when using GeoIP2.

9
README
View File

@ -205,10 +205,11 @@ To support storing configuration data for runtime-added zones in an LMDB
database, the server must be linked with liblmdb. If this is installed in database, the server must be linked with liblmdb. If this is installed in
a nonstandard location, specify the prefix using with-lmdb=/prefix. a nonstandard location, specify the prefix using with-lmdb=/prefix.
To support GeoIP location-based ACLs, the server must be linked with To support MaxMind GeoIP2 location-based ACLs, the server must be linked
libGeoIP. This is not turned on by default; BIND must be configured with with libmaxminddb. This is turned on by default if the library is found;
--with-geoip. If the library is installed in a nonstandard location, if the library is installed in a nonstandard location, specify the prefix
specify the prefix using --with-geoip=/prefix. using --with-maxminddb=/prefix. GeoIP2 support can be switched off with
--disable-geoip.
For DNSTAP packet logging, you must have installed libfstrm https:// For DNSTAP packet logging, you must have installed libfstrm https://
github.com/farsightsec/fstrm and libprotobuf-c https:// github.com/farsightsec/fstrm and libprotobuf-c https://

View File

@ -217,10 +217,11 @@ To support storing configuration data for runtime-added zones in an LMDB
database, the server must be linked with liblmdb. If this is installed in a database, the server must be linked with liblmdb. If this is installed in a
nonstandard location, specify the prefix using `with-lmdb=/prefix`. nonstandard location, specify the prefix using `with-lmdb=/prefix`.
To support GeoIP location-based ACLs, the server must be linked with To support MaxMind GeoIP2 location-based ACLs, the server must be linked
libGeoIP. This is not turned on by default; BIND must be configured with with `libmaxminddb`. This is turned on by default if the library is
`--with-geoip`. If the library is installed in a nonstandard location, found; if the library is installed in a nonstandard location,
specify the prefix using `--with-geoip=/prefix`. specify the prefix using `--with-maxminddb=/prefix`. GeoIP2 support
can be switched off with `--disable-geoip`.
For DNSTAP packet logging, you must have installed libfstrm For DNSTAP packet logging, you must have installed libfstrm
[https://github.com/farsightsec/fstrm](https://github.com/farsightsec/fstrm) [https://github.com/farsightsec/fstrm](https://github.com/farsightsec/fstrm)

View File

@ -4555,7 +4555,7 @@ badresp:1,adberr:0,findfail:0,valfail:0]
<listitem> <listitem>
<para> <para>
When <command>named</command> is compiled using the When <command>named</command> is compiled using the
MaxMind GeoIP2 geolocation API, or the legacy GeoIP API, MaxMind GeoIP2 geolocation API,
this specifies the directory containing GeoIP this specifies the directory containing GeoIP
database files. By default, the option is set based on database files. By default, the option is set based on
the prefix used to build the <command>libmaxminddb</command> the prefix used to build the <command>libmaxminddb</command>
@ -16864,9 +16864,7 @@ zone "example.com" {
specified, then these queries will be answered from the "city", specified, then these queries will be answered from the "city",
database if it is installed, or the "country" database if it database if it is installed, or the "country" database if it
is installed, in that order. Valid database names are is installed, in that order. Valid database names are
"country", "city", "asnum", "isp", and "domain". (If using "country", "city", "asnum", "isp", and "domain".
the legacy GeoIP API, "netspeed" and "org" databases are also
available.)
</para> </para>
<para> <para>
Some example GeoIP ACLs: Some example GeoIP ACLs:

View File

@ -118,11 +118,7 @@
The GeoIP2 API from MaxMind is now supported. Geolocation support The GeoIP2 API from MaxMind is now supported. Geolocation support
will be compiled in by default if the <command>libmaxminddb</command> will be compiled in by default if the <command>libmaxminddb</command>
library is found at compile time, but can be turned off by using library is found at compile time, but can be turned off by using
<command>configure --without-geoip2</command>, or by using <command>configure --without-geoip2</command>.
<command>configure --with-geoip</command>, which will cause
the legacy GeoIP API to be used instead. (Note that the
databases for the legacy API are no longer maintained by
MaxMind.)
</para> </para>
<para> <para>
The default path to the GeoIP2 databases will be set based The default path to the GeoIP2 databases will be set based
@ -141,7 +137,7 @@
types are <command>country</command>, <command>city</command>, types are <command>country</command>, <command>city</command>,
<command>domain</command>, <command>isp</command>, and <command>domain</command>, <command>isp</command>, and
<command>as</command>. All of these databases support both IPv4 <command>as</command>. All of these databases support both IPv4
and IPv6 lookups. [GL #182] and IPv6 lookups. [GL #182] [GL #1112]
</para> </para>
</listitem> </listitem>
<listitem> <listitem>