Lame Server messages

[Kevin Goddard]

I have looked around the net for some information on this error, but I have
not had much luck.
I get the following in my syslog for both my primary and secondary servers:
Jul 30 00:05:28 server27 named[12144]: Lame server on
'219.46.178.208.in-addr.arpa' (in '178.208.in-addr.arpa'?):
[206.251.8.20].53 'NS1.SNV1.GCTR.NET'
Jul 30 00:05:29 server27 named[12144]: Lame server on
'219.46.178.208.in-addr.arpa' (in '178.208.in-addr.arpa'?):
[204.152.166.154].53 'NS1.IAD1.GCTR.NET'
Jul 30 00:05:33 server27 named[12144]: Lame server on
'219.46.178.208.in-addr.arpa' (in '178.208.in-addr.arpa'?):
[205.216.163.20].53 'NS1.NUQ1.GCTR.NET'
Jul 30 00:14:56 server27 named[12144]: Lame server on
'212.46.178.208.in-addr.arpa' (in '178.208.in-addr.arpa'?): [206.41.7.71].53
'NS1.JFK1.GCTR.NET'

What is interesting is that the first two parts of my IP block is 208.178.
Now I don't have a 178.208.in-addr.arpa entry in either named.conf file.  I
actually turned off the entry for my reverse look up.  Here is my named.conf
file for the primary server:

// generated by named-bootconf.pl

options {
        directory "/var/named";
        check-names master warn;
};

zone "." {
        type hint;
        file "root.hints";
};

zone "0.0.127.in-addr.arpa" {
        type master;
        file "named.local";
};

zone "DOMAIN.com" {
        type master;
        file "DOMAIN.com";
};

//zone "208.178.46.in-addr.arpa" {
//      type master;
//      file "208.178.46";
file://};

Any ideas?

Kevin Goddard