Transfer openwebdevice.org domain to route53

RESOLVED FIXED

Status

Infrastructure & Operations
WebOps: SSL and Domain Names
RESOLVED FIXED
2 years ago
2 years ago

People

(Reporter: bensternthal, Assigned: cyliang)

Tracking

Details

(Whiteboard: [kanban:https://webops.kanbanize.com/ctrl_board/2/2316] )

(Reporter)

Description

2 years ago
We are moving http://openwebdevice.org/ from the paas to AWS (note its currently down, likely a problem with the PAAS but at this stage we dont care).

To support this please add the following CNAMES:

openwebdevice.org         openwebdevice.moz.works
www.openwebdevice.org     openwebdevice.moz.works
(Reporter)

Updated

2 years ago
Flags: needinfo?(cliang)

Updated

2 years ago
Whiteboard: [kanban:https://webops.kanbanize.com/ctrl_board/2/2316]
(Assignee)

Updated

2 years ago
Assignee: server-ops-webops → cliang
Flags: needinfo?(cliang)
(Assignee)

Comment 1

2 years ago
I've repointed the existing CNAME for www.openwebdevice.org to openwebdevice.moz.works.

Re-pointing openwebdevice.org is somewhat trickier; I'll need to double-check what we can actually do. 

My understanding is that CNAME records can't co-exist with other record types for the domain name; "root" domains (like openwebdevice.org) need NS (name server) and SOA (Start of Authority) records.  There are DNS providers that do some sleight of hand to work around this (CloudFlare comes to mind), but I'm not sure if the way Mozilla's DNS is currently constructed can do this.
(Assignee)

Comment 2

2 years ago
Okay.  Conferring with others, it sounds like we can't support CNAME flattening with the way DNS is handled at Mozilla.  If it's not safe to point to a particular IP for openwebdevice.org, we'll probably need to the openwebdevice.org domain moved over to Route 53 (where y'all can manage it directly).

Let me know if this needs to happen before the end of Mozlando.
(Reporter)

Comment 3

2 years ago
It can wait until next week. Many thanks for the help here.

Comment 4

2 years ago
(In reply to C. Liang [:cyliang] from comment #2)
> Okay.  Conferring with others, it sounds like we can't support CNAME
> flattening with the way DNS is handled at Mozilla.  If it's not safe to
> point to a particular IP for openwebdevice.org, we'll probably need to the
> openwebdevice.org domain moved over to Route 53 (where y'all can manage it
> directly).

Thanks C. You should have already the access you need to transfer the domain into route53 in the EE AWS account, and the docs[0] look fairly straightforward, but feel free to ping me if you have any questions.

[0] http://docs.aws.amazon.com/Route53/latest/DeveloperGuide/domain-transfer-to-route-53.html

Updated

2 years ago
Blocks: 1223989

Updated

2 years ago
Summary: Create CNAME to support http://openwebdevice.org/ being moved from PAAS to AWS → Transfer openwebdevice.org domain to route53
(Assignee)

Comment 5

2 years ago
The DNS setup for openwebdevice.org should now be similar to that of moz.works.  Please flag me down if you see something that is not working correctly.

* Hosted Route 53 zone set up in Engagement Engineering AWS account.
* Name servers repointed to AWS at domain registrar.
* openwebdevice.org zone delete from inventory control.
* Requested openwebdevice.org to be deleted from Akamai (may take up to 1 week)
Status: NEW → RESOLVED
Last Resolved: 2 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.