Closed
Bug 713951
Opened 14 years ago
Closed 14 years ago
IT bug - domain authorization letter, DNS configuration and more
Categories
(mozilla.org Graveyard :: Server Operations, task)
Tracking
(Not tracked)
RESOLVED
INCOMPLETE
People
(Reporter: smartin, Unassigned)
Details
(Whiteboard: [need more info])
A Mozilla vendor, Mediaplex, is working to implement first party cookies for Mozilla ads. The timeframe is in the next 4 weeks. They will need help from Mozilla IT on the signing of VeriSign Domain Authorization Letter, DNS configuration, etc. - see below.
Client (Mozilla) must provide/answer:
a) Client street address (where subdomain is registered to): 650 Castro Street, Mountain View, CA
b) MOJO Client ID and Client Name to be privately branded: Mozilla
c) Domain/subdomain to be used for Private Branding: media.mozilla.com
The subdomain should not currently be in use.
Terms such as ad, ads, marketing, etc. should not be used in the subdomain.
current client domain: website.com
example subdomain to be used: mktg.website.com
d) Will secure images be served or will conversion tags for secure pages be needed?
2) Mediaplex will request a Domain Authorization Letter from VeriSign and forward this letter to the client.
3) Client signs the VeriSign Domain Authorization Letter.
See Appendix A for example instructions and Domain Authorization Letter.
The Domain Authorization Letter must be printed on the letterhead of the DOMAIN REGISTRANT.
4) Client returns the signed and completed Domain Authorization letter to Mediaplex.
5) Mediaplex will submit the Domain Authorization Letter to VeriSign and wait for approval.
6) Once approved, Mediaplex will install/add the client’s privately branded domain to the MOJO Adserver.
7) Client must instruct their network/systems team to configure their DNS zone.
Client must configure the CNAME (canonical name) record to point to the following zone file: hostname.domain.com. IN CNAME private-branded.mplx.akadns.net.
8) If needed, Mediaplex will construct privately branded ROI/conversion tags, which match the domain name used in the privately branded publisher ad tags.
This will ensure impressions, clicks and ROI are within the same cookie space and proper correlation of activities to conversions will take place.
Updated•14 years ago
|
Assignee: nobody → network-operations
Component: Networking → Server Operations: Netops
Product: Core → mozilla.org
QA Contact: networking → mrz
Version: Other Branch → other
Updated•14 years ago
|
Assignee: network-operations → mrz
Component: Server Operations: Netops → Server Operations
QA Contact: mrz → cshields
Updated•14 years ago
|
Assignee: mrz → server-ops
Comment 1•14 years ago
|
||
What is the timeline for this? Looks like it got misassigned for a while, and you mentioned 4 weeks in the initial request.
Updated•14 years ago
|
Whiteboard: [need more info]
Comment 2•14 years ago
|
||
Triage :
Timeout. Please reopen with information asked for in comment #1.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → INCOMPLETE
Updated•11 years ago
|
Product: mozilla.org → mozilla.org Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•