You are viewing a plain text version of this content. The canonical link for it is here.
Posted to infrastructure-issues@apache.org by "Rodent of Unusual Size (JIRA)" <ji...@apache.org> on 2006/06/24 21:31:30 UTC
[jira] Updated: (INFRA-782) Need to switch nameservers for
apachecon.com urgently
[ http://issues.apache.org/jira/browse/INFRA-782?page=all ]
Rodent of Unusual Size updated INFRA-782:
-----------------------------------------
Attachment: ApacheCon.Com.db
Attached is the current ApacheCon.Com zone file. The Apache.Org servers should master the zone and replace the non-Apache nameservers for it. Some ApacheCon concom people need to be given access to the zone file and instructions on how to update it.
> Need to switch nameservers for apachecon.com urgently
> -----------------------------------------------------
>
> Key: INFRA-782
> URL: http://issues.apache.org/jira/browse/INFRA-782
> Project: Infrastructure
> Type: Bug
> Security: public(Regular issues)
> Components: DNS
> Reporter: Lars Eilebrecht
> Priority: Critical
> Attachments: ApacheCon.Com.db
>
> The apachecon.com is registered via dotser like all other apache domains, but we are still using the
> old nameservers.
> We have one lame nameserver (66.187.224.210 ns2.redhat.com) in the list and need to remove this
> one urgently!
> Removing the lame nameserver is just a workaround, the desired complete fix would be to completely switch all
> nameservers for apachecon.com to the same nameservers we also use for our apache.org domains.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira