Closed Bug 1283153 Opened 10 years ago Closed 10 years ago

Disable URL copy panel

Categories

(Cloud Services :: Operations: Miscellaneous, task)

task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: RT, Assigned: dmaher)

References

Details

User Story

The URL copy panel is currently exposed to 0% of Nightly, Aurora and Beta users as well as 0.4% of release users.
This bug is about bringing this back to 0% on all release types.

Set DNS record to

copy.loop.services.mozilla.com A 127.0.0.0
with TTL 604800

(Replacing the current 127.1.0.0 entry.)
No description provided.
User Story: (updated)
Depends on: 1239965
Ed, can you fill in the necessary details here?
Flags: needinfo?(edilee)
To prevent additional people from getting the feature, we can set the DNS entry to 127.0.0.0 to replace the current 127.1.0.0 record. I'm not sure what TTL to use as I don't expect us to be updating it much in the near future. copy.loop.services.mozilla.com A 127.0.0.0 abr/dmaher, do you know if just deleting the DNS A record will have it propagate or will some places try to keep its previous value? Any suggestions for either explicitly setting it to 127.0.0.0 or removing it (where either way will have Firefox not show the copy panel feature to users).
Blocks: 1268819
User Story: (updated)
Component: Client → Operations
Depends on: 1277184
Flags: needinfo?(edilee)
Flags: needinfo?(dmaher)
Flags: needinfo?(adam)
Product: Hello (Loop) → Cloud Services
The safe thing to do here, IMO, is to set it to 127.0.0.0. I would not count on NXDOMAIN propagation for this. (I say this based on my own lack of knowledge of the interaction of positive caching versus negative caching in intermediate DNS servers.) Given the current disposition of the service, I would set the TTL to 604800 seconds (i.e., one week).
Flags: needinfo?(dmaher)
Flags: needinfo?(adam)
Assignee: nobody → dmaher
User Story: (updated)
Agree with :abr. Setting copy.loop.services.m.c to 127.0.0.0 now. This will take effect within 30 minutes.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.