|
In the near future, SPEWS will publish lists that contain Domain Name Servers (DNS) used
by, or run by, spammers or spam supporters. These lists will allow anyone running their own
systems to invalidate domain name lookups that might otherwise go to these servers. This is
not to be confused with DNSBL email filtering or blocking, that method is covered on the SPEWS
Email Filtering page.
In theory, although a spammed email may get though, no one on that system will be able to
resolve and then visit spammer websites listed in the spam, or email replies to spammer
addresses contained in the spam.
We will probably start by providing tables for BIND 8.x and 9.x "named.conf" files and
add other DNS server deny methods as time goes by.
An example BIND listing would look something like this. Comments are located after the
double forward slashes (//):
server 216.144.208.200 { bogus yes; }; // dns1.dns4you.net
server 216.144.223.125 { bogus yes; }; // s01.dns.us.telodigm.net
server 216.144.223.126 { bogus yes; }; // s02.dns.us.telodigm.net
server 216.234.224.39 { bogus yes; }; // ns1.freehostweb.com
server 216.29.206.51 { bogus yes; }; // ns1.hostpower.net
server 216.29.206.52 { bogus yes; }; // ns2.hostpower.net
server 63.168.104.8 { bogus yes; }; // ns1.my-dns.net
server 64.39.30.189 { bogus yes; }; // ns1.tsunamipower.net
server 65.162.120.242 { bogus yes; }; // ns7.superspeeds.net
server 65.200.18.4 { bogus yes; }; // ns4.superspeeds.net
server 63.208.162.21 { bogus yes; }; // NS1.ENDERDNS.NET
server 63.208.162.26 { bogus yes; }; // NS2.ENDERDNS.NET
server 65.114.118.205 { bogus yes; }; // dns1.whodaonline.com
server 65.68.210.227 { bogus yes; }; // ns1.whodaonline.com
These examples were found in the ROKSO database
located at the Spamhaus Project.
Only individuals, companies, or internet service providers who run their own DNS servers
are able to filter using this method.
|
Menu
