Closed Bug 1280598 Opened 9 years ago Closed 9 years ago

Update mozilla.ch nameservers

Categories

(Infrastructure & Operations :: SSL Certificates, task)

Product:
Infrastructure & Operations
Component:
SSL Certificates
Type:
task
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: tanner, Assigned: rwatson)

References

Details

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

ns-1423.awsdns-49.org. ns-1814.awsdns-34.co.uk. ns-428.awsdns-53.com. ns-548.awsdns-04.net. Michael and/or nemo, please ack.
Whiteboard: [kanban:https://webops.kanbanize.com/ctrl_board/2/3138]
OK from me, but please first pull the docker image from the latest tag here: https://hub.docker.com/r/mozillach/mozilla.ch/tags/ Then let's move ahead and make this happen, great work!
Blocks: 1130862
Should updated to the latest version now.
Assignee: server-ops-webops → rwatson
:tanner did you complete the request by Michael? If so let me know and I"ll flip the switch
Flags: needinfo?(tanner.sumo.bugs)
I can confirm that the current version on https://mozillach.production.paas.mozilla.community/de is the updated one. Therefore we're ready to go here. Thank you!
dns updated.
Do you have a BIND file of the previous records, by chance?
Flags: needinfo?(tanner.sumo.bugs) → needinfo?(rwatson)
no bind file, but I logged the change: Changed nameservers from: [ns4-64.akam.net, ns7-66.akam.net, ns5-65.akam.net, ns1-240.akam.net] to: [ns-548.awsdns-04.net, ns-1814.awsdns-34.co.uk, ns-1423.awsdns-49.org, ns-428.awsdns-53.com]
Flags: needinfo?(rwatson)
mozilla.ch A 46.101.237.42 www.mozilla.ch A 46.101.237.42 mozilla.ch TXT google-site-verification=pAy11aa57yNock1wcPdkap3UiZAz4JRQzUGV4fEaQD4 mozilla.ch MX 1 ASPMX.L.GOOGLE.COM mozilla.ch MX 5 ALT1.ASPMX.L.GOOGLE.COM mozilla.ch MX 5 ALT2.ASPMX.L.GOOGLE.COM mozilla.ch MX 10 ASPMX2.GOOGLEMAIL.COM mozilla.ch MX 10 ASPMX3.GOOGLEMAIL.COM
Perfect, thanks a lot!
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.