Fwd: Frequent "Bogus LOOPBACK" errors with bind v8.2.3

[Steve Snyder]

Sorry to respond to my own messsage, but I thought another example of 
the problem I'm seeing might be helpful:

Feb  7 05:09:54 sunspot named[28111]: ns_forw: query(2.213.102.194.in-addr.arpa)
 Bogus LOOPBACK A RR (localhost:127.0.0.1) learnt (A=24.4.162.34:NS=24.4.162.34)
Feb  7 05:09:54 sunspot named[28111]: sysquery: query(localhost) Bogus LOOPBACK
A RR (localhost:127.0.0.1) learnt (A=24.4.162.34:NS=24.4.162.34)
Feb  7 05:09:54 sunspot named[28111]: sysquery: no addrs found for root NS
(localhost)
Feb  7 05:09:54 sunspot named[28111]: sysquery: query() Bogus LOOPBACK A RR
(localhost:127.0.0.1) learnt (A=24.4.162.34:NS=24.4.162.34)
Feb  7 05:09:54 sunspot named[28111]: sysquery: no addrs found for root NS ()

Thank you.

==================BEGIN FORWARDED MESSAGE==================

Hello.

Since updating to BIND v8.2.3 (from 8.2.2-P7) I've been getting a lot 
of these in my system log:

Feb  7 00:22:06 sunspot named[28111]: ns_forw: query(ftp.kernel.org) Bogus
LOOPBACK A RR (localhost:127.0.0.1) learnt (A=24.4.162.34:NS=24.4.162.34)
Feb  7 00:22:06 sunspot named[28111]: sysquery: query(localhost) Bogus LOOPBACK
A RR (localhost:127.0.0.1) learnt (A=24.4.162.34:NS=24.4.162.34)
Feb  7 00:22:06 sunspot named[28111]: sysquery: no addrs found for root NS
(localhost)
Feb  7 00:22:06 sunspot named[28111]: sysquery: query() Bogus LOOPBACK A RR
(localhost:127.0.0.1) learnt (A=24.4.162.34:NS=24.4.162.34)
Feb  7 00:22:06 sunspot named[28111]: sysquery: no addrs found for root NS ()

The text above is the result of ftp'ing to host ftp.kernel.org (but 
I've seen this with a number of different name resolutions).

This is on a Linux (RedHat v6.2 /w all released updates applied + 
kernel v2.2.18) system.  I've got BIND resolving names for my local 
LAN hosts and caching resolution for names outside my domain.  The 
address "24.4.162.34" you see above is one of my ISP's nameserver, 
used as a forwarder.

I'd be happy to list any of my config and/or zone files you'd like to 
see.  I'm enough of a newbie that I'm not sure which files are 
relevant to the problem I'm seeing.  To give all of you a general idea
of my setup, though, here is my named.conf:

options {
        directory "/var/named/snydernet";
        transfer-format many-answers;

        allow-query { 127.0.0.1; 192.168.0/24; };
        listen-on { 127.0.0.1; 192.168.0.1; };

        forward first;
        forwarders { 24.4.162.33; 24.4.162.34; };

        cleaning-interval 120;
        statistics-interval 120;
};

zone "0.0.127.IN-ADDR.ARPA" in {
        type master;
        file "db.127.0.0";
        notify no;
};

zone "snydernet.lan" in {
        type master;
        file "db.snydernet";
};

zone "0.168.192.IN-ADDR.ARPA" in {
        type master;
        file "db.192.168.0";
};

zone "." in {
        type hint;
        file "db.cache";
};


Any thoughts on this?  Thank you.


*** Steve Snyder ***
===================END FORWARDED MESSAGE===================


*** Steve Snyder ***