Closed Bug 1023433 Opened 12 years ago Closed 12 years ago

Please create a DNS entry pointing hotfix.telemetry.mozilla.org -> AWS Load Balanacer

Categories

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

task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: mreid, Assigned: cturra)

References

Details

Similar to bug 921167, please create a CNAME to point hotfix.telemetry.mozilla.org to the following AWS Load balancer: telemetry-hotfix-lb-710967824.us-west-2.elb.amazonaws.com (A Record) ipv6.telemetry-hotfix-lb-710967824.us-west-2.elb.amazonaws.com (AAAA Record) dualstack.telemetry-hotfix-lb-710967824.us-west-2.elb.amazonaws.com (A or AAAA Record) This load balancer is the entry point for the data submission system from bug 1019788.
OS: Mac OS X → All
Hardware: x86 → All
Blocks: 1019788
:mreid - i'd like to clarify your request. i can see that each of the A/AAAA records you've mentioned above are ELBs. it appears that you're asking hotfix.telemetry.mozilla.org to be a CNAME to all three? that won't actually be possible since CNAME records must be unique.
Flags: needinfo?(mreid)
They're all the same ELB, just different names for it. I never know what the state of ipv4 vs. ipv6 is, so I didn't know which one was best to use. I believe for the other telemetry endpoints, we used the 'dualstack' one, so let's do that here too. Please create the CNAME pointing to dualstack.telemetry-hotfix-lb-710967824.us-west-2.elb.amazonaws.com
Flags: needinfo?(mreid)
thnx for the clarification. i have added a cname for the dualstack A/AAAA record as requested. $ dig +short hotfix.telemetry.mozilla.org dualstack.telemetry-hotfix-lb-710967824.us-west-2.elb.amazonaws.com. 54.244.90.25 54.244.234.21
Assignee: server-ops-webops → cturra
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Blocks: 1075742
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in before you can comment on or make changes to this bug.