Closed Bug 1071815 Opened 11 years ago Closed 11 years ago

On evening of 9/29, setup DNS for advocacy.mozilla.org and setup a 301

Categories

(Infrastructure & Operations :: DNS and Domain Registration, task)

Product:
Infrastructure & Operations
Component:
DNS and Domain Registration
Platform:
x86
macOS
Type:
task
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: johns, Assigned: bhourigan)

References

Details

Hi there, On 9/29 or so we are going to be launching the advocacy.mozilla.org Wordpress instance. At that time, we'll need to: 1) Set a CNAME for advocacy.mozilla.org to advocacy-production-1393415359.us-east-1.elb.amazonaws.com 2) Setup/Turn on a 301 from mozilla.org/advocacy to the new advocacy.mozilla.org address.
Hi :jp Any reason we can't do step #1 earlier than the 30th?
No, go for it. I've not yet placed the node behind the elb, so we won't be leaking anything early. Thanks!
Hi Brian! Can you please go ahead and setup that DNS entry for advocacy.mozilla.org?
Status: NEW → ASSIGNED
Flags: needinfo?(bhourigan)
(In reply to JP Schneider :jp from comment #3) > Hi Brian! > > Can you please go ahead and setup that DNS entry for advocacy.mozilla.org? Good morning I went ahead and added the DNS entry, and I filed 1074206 for webops to change the redirect. I'll give it a couple hours and follow up with the webops team if it isn't done yet. Thanks for the ping.
Assignee: infra → bhourigan
Status: ASSIGNED → RESOLVED
Closed: 11 years ago
Flags: needinfo?(bhourigan)
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.