You are viewing a plain text version of this content. The canonical link for it is here.
Posted to infrastructure-issues@apache.org by "Chris Lambertus (JIRA)" <ji...@apache.org> on 2016/08/26 03:30:20 UTC

[jira] [Updated] (INFRA-12418) Advice and possible setup of DNS hosting

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

Chris Lambertus updated INFRA-12418:
------------------------------------
    Issue Type: Planned Work  (was: Task)

> Advice and possible setup of DNS hosting
> ----------------------------------------
>
>                 Key: INFRA-12418
>                 URL: https://issues.apache.org/jira/browse/INFRA-12418
>             Project: Infrastructure
>          Issue Type: Planned Work
>          Components: DNS
>            Reporter: Sidney Markowitz
>            Priority: Minor
>
> spamassassin.org domain currently is set up using our zone VM as a hidden master domain name server, publicly served by DNS donated by Sonic.net. I think they also donate the domain name registration. We can make changes to the DNS records in our svn, updating it on zone from where they are picked up by Sonic.net's nameservers.
> The current setup has been in place for quite a few years. SpamAssassin PMC would like Infra's opinion on whether it makes sense to continue with it or if there are now standard facilities for supporting project domains on Apache infrastructure and reasons for us to move our domain to them. If there are such reasons, how do we go about making the move?



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