Very OT: bind/named question

[dnsadmin 1bigthink.com]

Hello All,

I've a caching nameserver configured on my recently built CentOS 5.x 
mail server. The server is completely 'self-contained' as all mail 
and related processes are local on the box; no gateways.

I recently configured a similar box with CentOS 4.x this past year 
and have not seen this problem:

e.g.:

Dec  9 04:07:42 mxt named[3020]: FORMERR resolving 
'foxnewsmail.com.spintlink.net/AAAA/IN': 66.45.231.146#53
Dec  9 04:08:39 mxt named[3020]: FORMERR resolving 
'www.mailscanner.eu.spintlink.net/AAAA/IN': 64.20.52.34#53

I get many of these an hour. I'm not seeing real named problems, 
though. Mail seems to be flowing okay.

What if anything can I/should I do about this?

I've performed some searches on this topic and see that this can be 
related to IPV6 being enabled, but I believe I've disabled it. Also 
mentions of lame servers being at approximately 60-some-odd-percent 
Internet-wide and spammers with forged IPs causing these. That seems 
more likely; did the authors of bind just change the error message 
for lame servers to be more specific?

Your comments/suggestions appreciated.

Thanks,
Glenn


-- 
No virus found in this outgoing message.
Checked by AVG Free Edition. 
Version: 7.5.503 / Virus Database: 269.17.1/1183 - Release Date: 12/13/2007 9:15 AM



-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.