Your message dated Sat, 5 Sep 2015 17:12:33 -0400 with message-id <[email protected]> and subject line Re: Bug#181703: bind9: log entries don't specify remote IP has caused the Debian Bug report #181703, regarding bind9: log entries don't specify remote IP to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 181703: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=181703 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---ls: /etc/bind/db.0: No such file or directory ls: /etc/bind/db.255: No such file or directory Package: bind9 Version: 1:9.2.1-7 Severity: wishlist Recently I was plagued with log entries of the form: Feb 19 14:41:11 shakti named[20414]: received notify for zone 'scoopmedia.com': not authoritative Unfortunately, the log entry includes NO information as to who is sending the notify. Not very friendly. I ended up patching the source to make the log entry look like: Feb 19 14:41:11 shakti named[20414]: received notify for zone 'scoopmedia.com': not authoritative: client(192.67.14.16#44414) It was a quick and dirty patch, not meant for real use, but the idea is definitely the right thing to do. I should note that bind8 logs these entries with all kinds of extra info (including the IP) but bind9 does not. Anyway, if you want the patch I can generate it. This is most probably an upstream issue... -- System Information Debian Release: testing/unstable Kernel Version: Linux shakti 2.4.20-xfs-lvm #2 Wed Feb 19 04:36:31 PST 2003 i686 Pentium III (Katmai) GenuineIntel GNU/Linux Versions of the packages bind9 depends on: ii adduser 3.48 Add and remove users and groups ii libc6 2.3.1-8 GNU C Library: Shared libraries and Timezone ii libdns5 9.2.1-7 DNS Shared Library used by BIND ii libisc4 9.2.1-7 ISC Shared Library used by BIND ii libisccc0 9.2.1-7 Command Channel Library used by BIND ii libisccfg0 9.2.1-7 Config File Handling Library used by BIND ii liblwres1 9.2.1-7 Lightweight Resolver Library used by BIND ii libssl0.9.6 0.9.6g-6 SSL shared libraries ii netbase 4.08 Basic TCP/IP networking system --- Begin /etc/bind/named.conf (modified conffile) // This is the primary configuration file for the BIND DNS server named. // // Please read /usr/share/doc/bind9/README.Debian for information on the // structure of BIND configuration files in Debian, *BEFORE* you customize // this configuration file. // options { directory "/var/cache/bind"; // If there is a firewall between you and nameservers you want // to talk to, you might need to uncomment the query-source // directive below. Previous versions of BIND always asked // questions using port 53, but BIND 8.1 and later use an unprivileged // port by default. query-source address * port 53; // If your ISP provided one or more IP addresses for stable // nameservers, you probably want to use them as forwarders. // Uncomment the following block, and insert the addresses replacing // the all-0's placeholder. // forwarders { // 0.0.0.0; // }; auth-nxdomain no; # conform to RFC1035 }; // define a key - you should really change the secret since // all Debian boxes everywhere will have the same secret key "key" { algorithm hmac-md5; secret "snip"; }; // fortunately, using this control statement, we restrict access // to the control port 953/tcp to only the localhost and we // configure named to listen to 953 only on the lo interface controls { inet 127.0.0.1 allow { 127.0.0.1; } keys { "key"; }; }; // be authoritative for the localhost forward and reverse zones, and for // broadcast zones as per RFC 1912 view "internal" { match-clients { 192.168.1.0/24; 127.0.0.1/32; }; recursion yes; // prime the server with knowledge of the root servers zone "." { type hint; file "/etc/bind/db.root"; }; zone "localhost" { type master; file "/etc/bind/db.local"; }; zone "127.in-addr.arpa" { type master; file "/etc/bind/db.127"; }; zone "0.in-addr.arpa" { type master; file "/etc/bind/db.0"; }; zone "255.in-addr.arpa" { type master; file "/etc/bind/db.255"; }; // add entries for other zones below here zone "rupa.com" { type master; file "/etc/bind/db.rupa.com.int"; }; zone "1.168.192.in-addr.arpa" { type master; file "/etc/bind/db.192.168.1.0"; }; zone "gopigita.com" { type master; file "/etc/bind/db.stdwebsite.int"; }; zone "healingemstonejewelry.com" { type master; file "/etc/bind/db.stdwebsite.int"; }; zone "bisaha.com" { type master; file "/etc/bind/db.bisaha.com.int"; }; zone "gurukuli.com" { type slave; file "gurukuli.com.sec"; masters {65.243.113.102; 65.243.113.103; }; }; zone "vedicstudies.com" { type master; file "/etc/bind/db.stdwebsite.int"; }; }; view "external" { match-clients { any; }; recursion yes; // add entries for other zones below here zone "rupa.com" { type master; file "/etc/bind/db.rupa.com"; }; zone "gopigita.com" { type master; file "/etc/bind/db.stdwebsite"; }; zone "healingemstonejewelry.com" { type master; file "/etc/bind/db.stdwebsite"; }; zone "bisaha.com" { type master; file "/etc/bind/db.bisaha.com"; }; zone "vedicstudies.com" { type master; file "/etc/bind/db.stdwebsite"; }; zone "gurukuli.com" { type slave; file "gurukuli.com.sec"; masters {65.243.113.102; 65.243.113.103; }; }; }; --- End /etc/bind/named.conf --- Begin /etc/bind/db.0 (modified conffile) Config file not present or no permissions for access --- End /etc/bind/db.0 --- Begin /etc/bind/db.255 (modified conffile) Config file not present or no permissions for access --- End /etc/bind/db.255 -- -rupa
--- End Message ---
--- Begin Message ---Rupa Schomaker wrote: > Package: bind9 > Version: 1:9.2.1-7 > Severity: wishlist > > Recently I was plagued with log entries of the form: > > Feb 19 14:41:11 shakti named[20414]: received notify for zone > 'scoopmedia.com': not authoritative > > Unfortunately, the log entry includes NO information as to who is > sending the notify. Not very friendly. > > I ended up patching the source to make the log entry look like: > > Feb 19 14:41:11 shakti named[20414]: received notify for zone > 'scoopmedia.com': not authoritative: client(192.67.14.16#44414) > > It was a quick and dirty patch, not meant for real use, but the idea > is definitely the right thing to do. I should note that bind8 logs > these entries with all kinds of extra info (including the IP) but > bind9 does not. > > Anyway, if you want the patch I can generate it. This is most > probably an upstream issue... Hi, Rupa: Modern versions of BIND9 prefix this particular log message with the client's IP address and port number, so I'm closing this bug. -- Robert Edmonds [email protected]
--- End Message ---
