On Sunday, January 22, 2006, 1:49:41 PM, John DeMillion wrote:
Not sure when this happened, but a plain "w" somehow got listed in the SURBL, at least in the text list version. I've perused the website and the list removal section, but haven't found a way of determining what the source of the "w" is, since the query tools do domain format checking and won't let me query on a plain "w".
The "w" shows up in this list: http://www.surbl.org/dns-queries.blocklist.counts.txt It's in the section preceeded by the number "2".
The effect of this is that domains that have a "w" in certain places generate false positives.
It might be a good idea to run new domains through a simple domain format parsing check to make sure that they're basically valid before adding them to the SURBL.
John DeMillion Director of Information Technology Chester County Intermediate Unit
Hello John, "w" is not currently listed:
; <<>> DiG 8.3 <<>> w.multi.surbl.org a ;; res options: init recurs defnam dnsrch ;; got answer: ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 9855 ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0 ;; QUERY SECTION: ;; w.multi.surbl.org, type = A, class = IN
;; AUTHORITY SECTION: multi.surbl.org. 15M IN SOA a.surbl.org. zone.surbl.org. ( 1137979981 ; serial 15M ; refresh 15M ; retry 1W ; expiry 15M ) ; minimum
;; Total query time: 58 msec ;; FROM: ns1.freeapp.net to SERVER: 127.0.0.1 ;; WHEN: Sun Jan 22 17:52:58 2006 ;; MSG SIZE sent: 35 rcvd: 78
Doing a DNS query is probably the best, most authoritative way to check the lists.
What you saw may have been an artifact of broken DNS queries. There are also filters in place to prevent things that cannot be domains from getting on the lists.
Cheers,
Jeff C. -- Don't harm innocent bystanders.