Hello,
can someone explain, why the two packages - GeoIP - geoipupdate are needed when installing the bind-utils package?
yum install bind-utils ... ======================================================================================================================== Package Arch Version Repository Size ======================================================================================================================== Installing: bind-utils x86_64 32:9.11.4-26.P2.el7_9.2 base 260 k Installing for dependencies: GeoIP x86_64 1.5.0-14.el7 base 1.5 M bind-libs x86_64 32:9.11.4-26.P2.el7_9.2 base 157 k bind-libs-lite x86_64 32:9.11.4-26.P2.el7_9.2 base 1.1 M bind-license noarch 32:9.11.4-26.P2.el7_9.2 base 90 k geoipupdate x86_64 2.5.0-1.el7 base 35 k
Transaction Summary ======================================================================================================================== Install 1 Package (+5 Dependent packages) ...
Thanks,
Walter
On Tue, Dec 08, 2020 at 02:33:01PM +0100, Walter H. wrote:
can someone explain, why the two packages - GeoIP - geoipupdate are needed when installing the bind-utils package?
The bind-utils package requires 'libGeoIP.so.1()(64bit)', which is provided by the GeoIP package. The GeoIP package requires 'geoipupdate', which is provided by the geoipupdate package.
% rpm -q --requires bind-utils|grep GeoIP libGeoIP.so.1()(64bit) % rpm -q --requires GeoIP | grep geoipupdate geoipupdate
GeoIP provides a C library and a lookup tool to look up countries from an IP address. The bind-utils executables are all linked against libGeoIP.so.1, so I assume they use some functionality from that library.
/usr/bin/geoipupdate is a tool to update the data files in the GeoIP package.
On 08.12.2020 14:44, Jonathan Billings wrote:
On Tue, Dec 08, 2020 at 02:33:01PM +0100, Walter H. wrote:
can someone explain, why the two packages - GeoIP - geoipupdate are needed when installing the bind-utils package?
The bind-utils package requires 'libGeoIP.so.1()(64bit)', which is provided by the GeoIP package. The GeoIP package requires 'geoipupdate', which is provided by the geoipupdate package.
% rpm -q --requires bind-utils|grep GeoIP libGeoIP.so.1()(64bit) % rpm -q --requires GeoIP | grep geoipupdate geoipupdate
GeoIP provides a C library and a lookup tool to look up countries from an IP address. The bind-utils executables are all linked against libGeoIP.so.1, so I assume they use some functionality from that library.
/usr/bin/geoipupdate is a tool to update the data files in the GeoIP package.
Yes, then the interesting question, how can I make use of these GeoIP-features when doing these e.g.
nslookup 200:470:17:55::1 nslookup 222.10.10.1 nslookup www.centos.org host www.centos.org
Thanks, Walter
On Tue, Dec 08, 2020 at 02:54:03PM +0100, Walter H. wrote:
Yes, then the interesting question, how can I make use of these GeoIP-features when doing these e.g.
nslookup 200:470:17:55::1 nslookup 222.10.10.1 nslookup www.centos.org host www.centos.org
Looking at the source, it looks like the geoip-related functions are only called in the 'named' code and the libdns library. I don't see any features in dig, host or nslookup for looking up countries based on IP. However, the GeoIP package has a 'geoiplookup' command that looks up a country from an IP.
On 08.12.2020 15:12, Jonathan Billings wrote:
On Tue, Dec 08, 2020 at 02:54:03PM +0100, Walter H. wrote:
Yes, then the interesting question, how can I make use of these GeoIP-features when doing these e.g.
nslookup 200:470:17:55::1 nslookup 222.10.10.1 nslookup www.centos.org host www.centos.org
Looking at the source, it looks like the geoip-related functions are only called in the 'named' code and the libdns library. I don't see any features in dig, host or nslookup for looking up countries based on IP. However, the GeoIP package has a 'geoiplookup' command that looks up a country from an IP.
wouldn't it be a good idea to split this, so that 'bind-utils' has no dependency of neither GeoIP nor geoipupdate, like it is in CentOS 6?
(on systems where the bind-utils are used, mostly no GeoIP is used - DNS vs. Web)
Thanks,
Walter
On 12/9/20 1:28 AM, Walter H. wrote:
On 08.12.2020 15:12, Jonathan Billings wrote:
On Tue, Dec 08, 2020 at 02:54:03PM +0100, Walter H. wrote:
Yes, then the interesting question, how can I make use of these GeoIP-features when doing these e.g.
nslookup 200:470:17:55::1 nslookup 222.10.10.1 nslookup www.centos.org host www.centos.org
Looking at the source, it looks like the geoip-related functions are only called in the 'named' code and the libdns library. I don't see any features in dig, host or nslookup for looking up countries based on IP. However, the GeoIP package has a 'geoiplookup' command that looks up a country from an IP.
wouldn't it be a good idea to split this, so that 'bind-utils' has no dependency of neither GeoIP nor geoipupdate, like it is in CentOS 6?
(on systems where the bind-utils are used, mostly no GeoIP is used - DNS vs. Web)
Maybe .. but we don't design things .. we build source code. That is not a decision CentOS Linux makes.