Closed Bug 1273008 Opened 10 years ago Closed 10 years ago

Lower DNS TTL for treeherder.allizom.org

Categories

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

task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: emorley, Assigned: fubar)

References

Details

(Keywords: treeherder, Whiteboard: [kanban:https://webops.kanbanize.com/ctrl_board/2/2980] )

As part of bug 1176484, we'll soon be wanting to update the Treeherder DNS records to point to Heroku rather than the SCL3 instance. To make this switch easier on the day, it would help if we lower the DNS TTLs pre-emptively. Please could the current 1 hour TTL for treeherder.allizom.org be lowered to 60 seconds. Side note: Is it expected that treeherder.allizom.org has an A record (pointing to 63.245.215.125), whereas treeherder.mozilla.org is instead a CNAME (pointing to treeherder.vips.scl3.mozilla.com)? I would have expected for either both to be CNAMEs or else both to have an A record. Many thanks :-)
Whiteboard: [kanban:https://webops.kanbanize.com/ctrl_board/2/2980]
(In reply to Ed Morley [:emorley] from comment #0) > > Please could the current 1 hour TTL for treeherder.allizom.org be lowered to Done. > Side note: > Is it expected that treeherder.allizom.org has an A record (pointing to > 63.245.215.125), whereas treeherder.mozilla.org is instead a CNAME (pointing > to treeherder.vips.scl3.mozilla.com)? I would have expected for either both > to be CNAMEs or else both to have an A record. Hrm, dunno how that came to be. Replaced the A with a CNAME.
Assignee: server-ops-webops → klibby
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Many thanks :-)
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in before you can comment on or make changes to this bug.