Closed Bug 1044491 Opened 10 years ago Closed 10 years ago

Move badg.us to Route53

Categories

(Participation Infrastructure :: MCWS, task)

Product:
Participation Infrastructure
Component:
MCWS
Platform:
x86_64
Windows 8.1
Type:
task
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: jan, Assigned: tom)

References

Details

badg.us is running at 54.88.56.79 now, so the domain should point to it as well.
Depends on: 1040318
mrz owns this domain. I've created a record set in AWS. Since badg.us is hosted in AWS, it makes more sense to take advantage of Route53. @mrz, please can you point badg.us to: ns-1260.awsdns-29.org ns-1618.awsdns-10.co.uk ns-494.awsdns-61.com ns-873.awsdns-45.net Another option is for corporation to take ownership of the domain. We could file for that if you'd prefer. @Jan So that we can auto-scale, we should point this to a load balancer. I've created csa-badgus-production. Once I've confirmed that the load balancer works with badg.us, shall I point it at the load balancer? We can't achieve high availability without it.
Summary: Point badg.us to 54.88.56.79 → Move badg.us to Route53
Nothing in this bug pointed to me and it was never on my radar. Are you ready to take the NS RRs for this domain?
Yep, we're ready to take them.
GoDaddy updated.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED

Bulk move of bugs

Component: Community IT → MCWS
Product: Infrastructure & Operations → Participation Infrastructure
You need to log in before you can comment on or make changes to this bug.