|Main Archive Page > Month Archives > spamassassin-dev archives|
--- Comment #1 from Mark Martinec <Mark.Martinec@ijs.si> 2011-11-30 17:53:26 UTC ---
> I've been working over the past few weeks to get the IPv6 infrastructure setup
> and we are now testing an IPv6 nameserver (ns3.pccc.com).
Very nice to hear.
> If things go as planned, I believe we will need to add this nameserver to the
> spamassassin.org zone so that there is an IPv6 resolver in the mix of domain
We may, but it is not a requirement. Seems like the three slave DNS servers
at sonic.net for domain spamassassin.org already have dual-stack connectivity:
$ host -t ns spamassassin.org
spamassassin.org name server a.auth-ns.sonic.net.
spamassassin.org name server c.auth-ns.sonic.net.
spamassassin.org name server b.auth-ns.sonic.net.
spamassassin.org name server ns.hyperreal.org.
$ host a.auth-ns.sonic.net
a.auth-ns.sonic.net has address 22.214.171.124
a.auth-ns.sonic.net has IPv6 address 2001:5a8:0:3::1
$ host b.auth-ns.sonic.net
b.auth-ns.sonic.net has address 126.96.36.199
b.auth-ns.sonic.net has IPv6 address 2607:f0d0:1102:f::2
$ host c.auth-ns.sonic.net
c.auth-ns.sonic.net has address 188.8.131.52
c.auth-ns.sonic.net has IPv6 address 2001:48c8:1:1::2
The ns.hyperreal.org is still IPv4-only, but that doesn't matter.
> Then we plan to add a record for AAAA that points to the sa-update.pccc.com
> working on IPv6 to get the MIRRORED_BY file so that sa-update can work on a
> pure IPv6 network.
Yes, this is still needed. It is the only reason preventing sa-update
from bootstraping on such node. Perhaps it is now the time do this step.
Existing/old sa-update won't notice the AAAA record, the new sa-update
will take advantage of it when possible/necessary.
During the past few days I have prepared another fresh node with inet6
connectivity only for testing SpamAssassin. Looks fine.
Btw, dealing with IPv4-only RBL servers, the solution is DNS64 + NAT64.
The DNS64 is running fine (available since bind 9.8), but the NAT64 is
still giving me hard time.
Is anything else besides MIRRORED.BY tied to spamassassin.apache.org ?
So, is everybody happy about adding AAAA to spamassassin.apache.org,
pointing to 2001:550:2a00:1::2 ( = www.sa-update.pccc.com) ?
Or do we bug infra again about the progress in making apache.org
-- Configure bugmail: https://issues.apache.org/SpamAssassin/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.