Closed Bug 1222882 Opened 11 years ago Closed 10 years ago

Update DNS for bugzfeed.mozilla.org to point to Heroku

Categories

(Infrastructure & Operations Graveyard :: WebOps: Other, task)

task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: mcote, Assigned: cliang)

References

Details

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

As per bug 952881, we're moving Bugzfeed (the WebSockets bug-update-notification service) to Heroku. I've got it all set up there, include the SSL certs; I just need DNS switched over. The project is under Mozilla's Heroku account and is named "bugzfeed". This can be done at any time. Thanks!
Whiteboard: [kanban:https://webops.kanbanize.com/ctrl_board/2/2155]
Assignee: server-ops-webops → cliang
Changed bugzfeed.mozilla.org from an A record: bugzfeed.mozilla.org A 54.241.166.68 to a CNAME: bugzfeed.mozilla.org CNAME bugzfeed.herokuapp.com Please let me know if this causes you any issues.
Blocks: 952881
Ah sorry, Heroku has a special SSL endpoint for apps[1]. In bugzfeed's case it's nagasaki-5623.herokussl.com. Please update the CNAME for bugzfeed.mozilla.org to point to that domain instead of bugzfeed.herokuapp.com. I've also just added the domain to the app, as specified in [1]. [1] https://devcenter.heroku.com/articles/ssl-endpoint
Updated. This should start percolating through DNS shortly. Do you still need bugzfeed-dev.allizom.org or should that be repointed to something else as well?
Ah no, I wrapped that functionality into the main bugzfeed app. You can remove that DNS entry entirely; I'll make sure the corresponding AWS host is destroyed.
Great, this is working perfectly, both SSL and non-SSL. Thanks!
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
* Removed A record for bugzfeed-dev.allizom.org
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in before you can comment on or make changes to this bug.