[jira] [Updated] (INFRA-2507) ASF-ify the spamassassin.org DNS hosting

["Gavin (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/INFRA-2507?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gavin updated INFRA-2507:
-------------------------
    Issue Type: Planned Work  (was: Task)

> ASF-ify the spamassassin.org DNS hosting
> ----------------------------------------
>
>                 Key: INFRA-2507
>                 URL: https://issues.apache.org/jira/browse/INFRA-2507
>             Project: Infrastructure
>          Issue Type: Planned Work
>      Security Level: public(Regular issues) 
>            Reporter: Daryl C. W. O'Shea
>            Assignee: Daniel Gruno
>            Priority: Minor
>
> As discussed in the thread "Moving spamassassin.org DNS zone to ASF DNS servers - the redux" on infra@ on Jan 22-25, 2010, the SpamAssassin PMC would like to get the spamassassin.org domain's DNS zone hosted on the same infrastructure as the other ASF domains.
> Also, as discussed, we need a way to automatically reload the zone file since our automated rule update infrastructure depends on being able to update DNS records to publish the rule updates.
> Ideally we'd split the zone up into spamassassin.org and updates.spamassassin.org as automatic updates only happen to updates.spamassassin.org.  We could get by without, but it'd be icing on the cake.
> We'd also like to consider allowing zone transfers to sonic.net's name servers.  I think keeping them as slave name servers wouldn't be a bad idea.  Their IPs are 209.204.159.20, 64.142.88.72 and 69.9.186.104.
> We'll also need to figure out how exactly we want the automatic reloads of the updates.spamassassin.org zone to happen.  There's dozens of ways to do it (frequent cron job (every 15 minutes?), svn commit hook, etc)... whatever fits in with the current security policy works for me.
> Thanks,
> Daryl



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)