www-infrastructure-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Lambertus (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (INFRA-12418) Advice and possible setup of DNS hosting
Date Fri, 26 Aug 2016 03:30:20 GMT

    [ https://issues.apache.org/jira/browse/INFRA-12418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15438405#comment-15438405

Chris Lambertus commented on INFRA-12418:

There is precedent for infra hosting DNS for projects. We'd want to get the zone files set
up on our end first, then we'd need to notify our secondary DNS providers of the new zone.
Once that's all done and validated, whoever owns the spamassassin.org zone now would need
to transfer it to us. 

> Advice and possible setup of DNS hosting
> ----------------------------------------
>                 Key: INFRA-12418
>                 URL: https://issues.apache.org/jira/browse/INFRA-12418
>             Project: Infrastructure
>          Issue Type: Task
>          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

View raw message