Closed
Bug 1495719
Opened 7 years ago
Closed 7 years ago
Point health.graphics to https://firefox-health-dashboard.netlify.com
Categories
(Infrastructure & Operations :: DNS and Domain Registration, task)
Infrastructure & Operations
DNS and Domain Registration
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: armenzg, Assigned: rtucker)
Details
(Whiteboard: [kanban:https://webops.kanbanize.com/ctrl_board/19/7055])
Same kind of work as on bug 1488533.
Does this info help? (it's from Netlify configurations)
> health.graphics ALIAS firefox-health-dashboard.netlify.com.
| Assignee | ||
Updated•7 years ago
|
Assignee: infra → rtucker
| Assignee | ||
Comment 1•7 years ago
|
||
host -t ns health.graphics
health.graphics name server marek.ns.cloudflare.com.
health.graphics name server kia.ns.cloudflare.com.
| Assignee | ||
Comment 2•7 years ago
|
||
(In reply to Armen [:armenzg] from comment #0)
> Same kind of work as on bug 1488533.
>
> Does this info help? (it's from Netlify configurations)
>
> > health.graphics ALIAS firefox-health-dashboard.netlify.com.
I don't see health.graphics in markmonitor.
I'm not sure how to proceed as I can't tell who owns this domain. All of the whois is protected.
| Reporter | ||
Comment 3•7 years ago
|
||
Hi Rob, let me look for the owner and I will get back to you.
| Reporter | ||
Comment 4•7 years ago
|
||
Rob, what info do you need for the domain to be transfered to Mozilla?
Hi Harald, would you mind helping Rob complete the transfer?
Flags: needinfo?(hkirschner)
Comment 5•7 years ago
|
||
Sure, let me know the details for the DNS and any other changes I need to make.
Flags: needinfo?(hkirschner)
| Assignee | ||
Comment 6•7 years ago
|
||
Is the goal to transfer the domain into mozilla ownership or simply change DNS entries?
If you just need to update DNS, then that doesn't need my involvement.
| Reporter | ||
Comment 7•7 years ago
|
||
I'm personally interested on transferring to Mozilla so we have a team that could tackle changes like this in the future.
Comment 8•7 years ago
|
||
Bulk reset of QA contacts in Infra and Ops bugs.
https://bugzilla.mozilla.org/show_bug.cgi?id=1495849
QA Contact: smani → cshields
| Reporter | ||
Comment 9•7 years ago
|
||
Harald, would you mind passing ownership of the domain to IT?
Rob, what information would Harald need to transfer the domain?
Thanks!
Flags: needinfo?(hkirschner)
Comment 10•7 years ago
|
||
Armen, I'm not convinced this is a domain that Mozilla needs to own yet. What's the business case here?
Flags: needinfo?(armenzg)
| Reporter | ||
Comment 11•7 years ago
|
||
What would be the requirements for a domain to be owned by Mozilla?
It's being used by product managers to track the health of our Firefox products.
Flags: needinfo?(armenzg)
Comment 12•7 years ago
|
||
How was past domain prolifiration for arewe*yet.com domains handled?
I don't see harm in PMs opening the netlify URL or a mzl.la we create.
Flags: needinfo?(hkirschner)
| Reporter | ||
Comment 13•7 years ago
|
||
If somebody helps me use a mzl.la one I would gladly use that.
Comment 14•7 years ago
|
||
mzl.la short URLs are generated by Bit.ly. I think the mzl.la short URLs are restricted to the mozilla.org domain, so we couldn't point one to firefox-health-dashboard.netlify.com.
Comment 15•7 years ago
|
||
Sorry guys, I let this drop.
(In reply to Armen [:armenzg] from comment #11)
> What would be the requirements for a domain to be owned by Mozilla?
>
> It's being used by product managers to track the health of our Firefox
> products.
Is there an issue with sending product managers the https://firefox-health-dashboard.netlify.com/ url to use?
Context is that we are trying to trim down the domains we own and have to maintain. If there's a strong need for the domain I'll get it but if it is a matter of convenience for a small group can we pass?
Flags: needinfo?(armenzg)
| Reporter | ||
Comment 16•7 years ago
|
||
It's not a problem.
I keep referring them to the new domain. Thanks!
Status: NEW → RESOLVED
Closed: 7 years ago
Flags: needinfo?(armenzg)
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•