You are viewing a plain text version of this content. The canonical link for it is here.
Posted to infrastructure-issues@apache.org by "Lars Eilebrecht (JIRA)" <ji...@apache.org> on 2006/05/02 15:00:46 UTC
[jira] Created: (INFRA-782) Need to switch nameservers for
apachecon.com urgently
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
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
[jira] Commented: (INFRA-782) Need to switch nameservers for
apachecon.com urgently
Posted by "Lars Eilebrecht (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/INFRA-782?page=comments#action_12414825 ]
Lars Eilebrecht commented on INFRA-782:
---------------------------------------
The lame nameserver has been fixed, but we still need to migrate the domain
to the regular ASF name servers.
> 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
>
> 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
[jira] Closed: (INFRA-782) Need to switch nameservers for
apachecon.com urgently
Posted by "Joe Schaefer (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/INFRA-782?page=all ]
Joe Schaefer closed INFRA-782:
------------------------------
Resolution: Fixed
dnsadmin group created on minotaur. We are handling
the apachecon.com zone now. Folks who want to share
administration duties for our dns zones should read
https://svn.apache.org/repos/asf/infrastructure/trunk/dns/README
> 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
[jira] Updated: (INFRA-782) Need to switch nameservers for
apachecon.com urgently
Posted by "Rodent of Unusual Size (JIRA)" <ji...@apache.org>.
[ 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