On Wednesday, April 28, 2004, 12:40:57 AM, Raymond Dijkxhoorn wrote:
Hi!
sbl-xbl -r/var/named/spamhaus -t21600 -c60 -b127.0.0.1/230 \ sbl-xbl.spamhaus.org:ip4set:sbl \ sbl-xbl.spamhaus.org:ip4set:xbl \
Hmm, what does that mean in terms of the presence of $SOA and $NS in each rbldnsd zone file? Do those help or hurt what you do above?
I dont use them, but they also supply:
[root@vmx01 spamhaus]# more xbl-extras $SOA 3600 need.to.know.only. hostmaster.spamhaus.org. 0 1h 10m 5d 1200 $NS 86400 a.ns.spamhaus.org c.ns.spamhaus.org e.ns.spamhaus.org f.ns.spamhaus.org g.ns.spamhaus.org m.ns.spamhaus.org n.ns.spamhaus.org q.ns.spamhaus.org t.ns.spamhaus.org w.ns.spamhaus.org x.ns.spamhaus.org y.ns.spamhaus.org z.ns.spamhaus.org $NS 86400 c.ns.spamhaus.org
...
$NS 86400 y.ns.spamhaus.org $NS 86400 z.ns.spamhaus.org
(Any ideas why they list c through z twice?)
So people who want them can also load them up.
They are not needed for rbldnsd to function however.
Hmm, that's pretty much what Mark Reynolds was asking for earlier: rbldnsd headers and domains supplied separately.
Should we perhaps offer them separately also, in addition to the existing complete rbldnsd zone files?
I suppose our "extras" could include the testpoints and @ record, as in (basically the top of the file but not the spam domains):
$SOA 600 ns1.freeapp.net zone.surbl.org 1083137775 600 300 604800 600 $NS 600 ns1.surbl.org ns2.surbl.org ns3.surbl.org ns4.surbl.org ns5.surbl.org ns 6.surbl.org ns7.surbl.org ns8.surbl.org ns9.surbl.org ns10.surbl.org ns11.surbl. org ns12.surbl.org ns13.surbl.org ns14.surbl.org :127.0.0.2:Message body contains SpamCop spamvertised domain. @ 66.170.2.60 test.surbl.org :2:sc.surbl.org permanent test point test.sc.surbl.org :2:sc.surbl.org permanent test point surbl-org-permanent-test-point.com :2:sc.surbl.org permanent test point 2.0.0.127 :2:sc.surbl.org permanent test point
We could name such new files with something like:
sc.surbl.org.headers.rbldnsd sc.surbl.org.domains.rbldnsd
Jeff C.