Closed Bug 921167 Opened 12 years ago Closed 12 years ago

Change DNS "incoming.telemetry.mozilla.org" to point at AWS load balancer

Categories

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

Product:
Infrastructure & Operations Graveyard
Component:
WebOps: Other
Type:
task

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: mreid, Assigned: bburton)

References

Details

On October 1, when we cut over to the new telemetry server, the DNS entry for incoming.telemetry.mozilla.org should be updated to point at the production AWS load balancer. DNS info for the target AWS load balancer: telemetry-server-lb-2038738656.us-west-2.elb.amazonaws.com (A Record) ipv6.telemetry-server-lb-2038738656.us-west-2.elb.amazonaws.com (AAAA Record) dualstack.telemetry-server-lb-2038738656.us-west-2.elb.amazonaws.com (A or AAAA Record) Please check with :mreid before pulling the trigger :)
Blocks: 921161
See Also: → 911309
I'm on point for this, I'll try to keep an eye on bugmail but feel free to ping me on IRC when this is ready to go
Assignee: server-ops-webops → bburton
Priority: -- → P1
We're ready to go on this - please make the change when you're ready.
Changes committed, should be live in 10-15 minutes +/- caching
Status: NEW → ASSIGNED
DNS was updated to be a CNAME to dualstack.telemetry-server-lb-2038738656.us-west-2.elb.amazonaws.com
I am seeing the new record -> % dig incoming.telemetry.mozilla.org ; <<>> DiG 9.8.3-P1 <<>> incoming.telemetry.mozilla.org ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 30634 ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 8, ADDITIONAL: 8 ;; QUESTION SECTION: ;incoming.telemetry.mozilla.org. IN A ;; ANSWER SECTION: incoming.telemetry.mozilla.org. 60 IN CNAME dualstack.telemetry-server-lb-2038738656.us-west-2.elb.amazonaws.com. dualstack.telemetry-server-lb-2038738656.us-west-2.elb.amazonaws.com. 60 IN A 54.244.220.253 ;; AUTHORITY SECTION: us-west-2.elb.amazonaws.com. 10 IN NS ns-935.amazonaws.com. us-west-2.elb.amazonaws.com. 10 IN NS ns-916.amazonaws.com. us-west-2.elb.amazonaws.com. 10 IN NS ns-941.amazonaws.com. us-west-2.elb.amazonaws.com. 10 IN NS ns-925.amazonaws.com. us-west-2.elb.amazonaws.com. 10 IN NS ns-944.amazonaws.com. us-west-2.elb.amazonaws.com. 10 IN NS ns-927.amazonaws.com. us-west-2.elb.amazonaws.com. 10 IN NS ns-934.amazonaws.com. us-west-2.elb.amazonaws.com. 10 IN NS ns-947.amazonaws.com. ;; ADDITIONAL SECTION: ns-927.amazonaws.com. 310 IN A 72.21.204.209 ns-935.amazonaws.com. 310 IN A 87.238.80.213 ns-947.amazonaws.com. 310 IN A 204.246.162.10 ns-925.amazonaws.com. 310 IN A 72.21.208.213 ns-934.amazonaws.com. 310 IN A 87.238.84.215 ns-944.amazonaws.com. 14501 IN A 205.251.228.6 ns-941.amazonaws.com. 14501 IN A 204.246.160.5 ns-916.amazonaws.com. 298 IN A 207.171.178.7 ;; Query time: 81 msec ;; SERVER: 10.8.75.21#53(10.8.75.21) ;; WHEN: Tue Oct 1 09:15:27 2013 ;; MSG SIZE rcvd: 442 bburton@althalus [09:15:27] [~] -> %
confirmed we're seeing submissions!
Status: ASSIGNED → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Component: Server Operations: Web Operations → WebOps: Other
Product: mozilla.org → Infrastructure & Operations
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in before you can comment on or make changes to this bug.