I see "server failures" on a bunch of obviously fake hostnames:
WARNING: DNS server 216.12.134.208 returned a SERVER FAILURE error for MX or A for Me.
WARNING: DNS server 216.12.134.208 returned a SERVER FAILURE error for MX or A for host3.
WARNING: DNS server 216.12.134.208 returned a SERVER FAILURE error for MX or A for mailer1.
WARNING: DNS server 216.12.134.208 returned a SERVER FAILURE error for MX or A for jinge.
...Anything we can do to add a weight to these? We do also see server failures on some hostnames were do have an A record, so I see the delema. But it would be nice to at least add a weighting to the obvious fakes.
That's definitely a problem with the DNS server -- the "server failure" indicates "a problem with the nameserver". For hosts that are not fully qualified (such as "Me"), the DNS server should be reporting that the host does not exist. In fact, it's possible for "Me" to have an MX record someday (unlikely, as there would need to be a country that used the .me ccTLD, and it would need to be set up to accept mail, but it could happen), so your DNS server technically should be contacting the root servers for these. Although it is understandable that your DNS server does not look them up (the root servers get overwhelmed by these bogus lookups, whether caused by a spammer, or someone typing "www.microsoft.cmo" into their web browser), it should not be returning a server failure message.
For the non-fully-qualified host names, we might be able to automatically check for that, which would get around this problem.
-Scott
--- [This E-mail was scanned for viruses by Declude Virus (http://www.declude.com)]
--- This E-mail came from the Declude.JunkMail mailing list. To unsubscribe, just send an E-mail to [EMAIL PROTECTED], and type "unsubscribe Declude.JunkMail". The archives can be found at http://www.mail-archive.com.
