Contributed by jose on from the spamland-security dept.
If the network allows, you could nest another dns server behind your real one. This server would have all of your 'real' zones replicated, but only be serving queries that come from the blacklist (as redirected by your real dns server).
Now, set up some mx records for the zones on the false machine to point to 127.0.0.1, 192.168.1.1, 10.0.0.1, etc.
I'm not sure if this would be as disruptive as spamd would be, but it would have messages ricocheting around the inside for a while!" This idea is sort of interesting. Anyone work with something like this to potentially propogate invalid information back to spammers (ie false MX records)?
(Comments are closed)
By Angry Rodent () on
By BSE () on
By Passerby () on
dnsreflector is a daemon that listens for DNS queries on a
local UDP port and answers with records pointing back to
localhost.
Combined with pf(4) this works as a bandwidth efficient spamtrap.
WWW: ${HOMEPAGE}
By Brent Graveland () brent@graveland.net on http://graveland.net/
I guess since spews tends to block whole ISP's who are spam friendly, it may work.
Still, with the distributed and caching nature of DNS, I wouldn't want bad DNS data out there.
Besides, I like spamd :) In the last 2 days, I've wasted 59 hours of spammer MTA time on my 2 MX hosts.
By NYB () spam@localhost on http://spews.org/faq.html
Comments
By Can Erkin Acar () on http://www.benzedrine.cx/relaydb.html
Daniel did: http://www.benzedrine.cx/relaydb.html :)
By Anonymous Coward () on
By thehoodbuddy () on
don't have to deal with reloads.