You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@infra.apache.org by "#asfinfra Bot (JIRA)" <ji...@apache.org> on 2016/09/08 13:55:20 UTC
[jira] [Closed] (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 ]
#asfinfra Bot closed INFRA-12418.
---------------------------------
Resolution: Won't Fix (was: Unresolved)
Hi,
This issue has been in state 'Pending Closed' for at least 5 days, and was previously waiting for at least 3 days for waiting for updates.
We are closing this issue automatically, feel free to reopen the issue or open a new one should you need further help.
--
Cheers,
Apache Infrastructure Team
> 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)