spamassassin-dev November 2011 archive
Main Archive Page > Month Archives  > spamassassin-dev archives
spamassassin-dev: [Bug 6712] IPv6 DNS Work

[Bug 6712] IPv6 DNS Work

From: <bugzilla-daemon_at_nospam>
Date: Wed Nov 30 2011 - 17:53:26 GMT

--- Comment #1 from Mark Martinec <> 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 (

Very nice to hear.

> If things go as planned, I believe we will need to add this nameserver to the
> zone so that there is an IPv6 resolver in the mix of domain
> names.

We may, but it is not a requirement. Seems like the three slave DNS servers
at for domain already have dual-stack connectivity:

$ host -t ns name server name server name server name server

$ host has address has IPv6 address 2001:5a8:0:3::1

$ host has address has IPv6 address 2607:f0d0:1102:f::2

$ host has address has IPv6 address 2001:48c8:1:1::2

The is still IPv4-only, but that doesn't matter.

> Then we plan to add a record for AAAA that points to the
> 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 ?

So, is everybody happy about adding AAAA to,
pointing to 2001:550:2a00:1::2 ( = ?
Or do we bug infra again about the progress in making
dual stacked.

-- Configure bugmail: ------- You are receiving this mail because: ------- You are the assignee for the bug.