GeoIP in BIND

Issues related to configuring your network
Post Reply
MartinR
Posts: 714
Joined: 2015/05/11 07:53:27
Location: UK

GeoIP in BIND

Post by MartinR » 2019/05/16 10:52:21

When BIND starts up (CentOS 7.6, BIND 9.9.4-RedHat-9.9.4-73.el7_6) I see the following messages:

Code: Select all

named[6041]: initializing GeoIP Country (IPv4) (type 1) DB
named[6041]: GEO-106FREE 20180327 Build 1 Copyright (c) 2018 MaxMind Inc All Rights Reserved
named[6041]: initializing GeoIP Country (IPv6) (type 12) DB
named[6041]: GEO-106FREE 20180605 Build 1 Copyright (c) 2018 MaxMind Inc All Rights Reserved
named[6041]: GeoIP City (IPv4) (type 2) DB not available
named[6041]: GeoIP City (IPv4) (type 6) DB not available
named[6041]: GeoIP City (IPv6) (type 30) DB not available
named[6041]: GeoIP City (IPv6) (type 31) DB not available
named[6041]: GeoIP Region (type 3) DB not available
named[6041]: GeoIP Region (type 7) DB not available
named[6041]: GeoIP ISP (type 4) DB not available
named[6041]: GeoIP Org (type 5) DB not available
named[6041]: GeoIP AS (type 9) DB not available
named[6041]: GeoIP Domain (type 11) DB not available
named[6041]: GeoIP NetSpeed (type 10) DB not available
According to ISC, GeoIP support is only available from 9.10, however I notice that the default 9.9 was built with --with-geoip. Is there any simple way to turn off GeoIP within BIND? Specifically I'm trying to eradicate all non-error error messages from logwatch.

yum remove brings up a lot of dependencies. I've checked my /etc/named.conf and there is no mention of GeoIP (# grep -i geo named* named*/*). /etc/sysconfig/named is nothing but comment lines.

/var/named/log/named.log does contain two lines mentioning geo:

Code: Select all

16-May-2019 08:50:05.024 lame-servers: info: network unreachable resolving 'status.geotrust.com/AAAA/IN': 2001:502:cbe4::33#53
16-May-2019 08:50:05.025 lame-servers: info: network unreachable resolving 'status.geotrust.com/AAAA/IN': 2620:74:19::33#53
Low priority, this is more of an annoying itch than a real problem.

User avatar
avij
Retired Moderator
Posts: 3046
Joined: 2010/12/01 19:25:52
Location: Helsinki, Finland
Contact:

Re: GeoIP in BIND

Post by avij » 2019/05/16 13:28:43

Short of rebuilding bind without that build option, I don't think there's a way to silence those notices.

MartinR
Posts: 714
Joined: 2015/05/11 07:53:27
Location: UK

Re: GeoIP in BIND

Post by MartinR » 2019/05/16 14:21:41

I'll probably end up modifying the service definition in logwatch then. Thanks.

zv4
Posts: 1
Joined: 2022/08/20 21:06:13

Re: GeoIP in BIND

Post by zv4 » 2022/08/20 21:09:49

MartinR wrote:
2019/05/16 14:21:41
I'll probably end up modifying the service definition in logwatch then. Thanks.
Might you be such a gentleman to share the nodifications to the service definition?

I copied /usr/share/logwatch/default.conf/services/named.conf into /etc/logwatch/conf/services/ but its not clear where to add these fitlers.

Post Reply