Establish internal org and product team hosting/DNS strategy

[jcklpe]

Goal

Establish a straightforward, organization-owned approach to hosting and DNS so Product Teams can obtain durable infrastructure without depending on undocumented personal accounts. Implementation may require a future budget amendment.

This is the umbrella issue for organization-owned hosting and DNS:

• Establish org wide DNS policy #509 — organization-wide DNS policy
• Establish org wide hosting policy #510 — organization-wide hosting policy
• Transfer ownership of Landlord Mapper domain to Infrastructure #508 — Landlord Mapper domain transfer
• Unstick the backend issues with Landlord Mapper #511 — Landlord Mapper backend unblock

Questions to resolve

• What should Open Austin own directly, and what may remain project-managed?
• Which providers or service patterns should be supported?
• Who may approve expenses and administrative access?
• Where should credentials and recovery information live?
• What backup, export, handoff, and project-inactivity expectations apply?
• How can a Product Team request infrastructure without needing private organizational context?

Definition of done

• A practical hosting/DNS strategy is documented.
• Ownership, access, cost, and handoff expectations are clear.
• The Landlord Mapper pilot informs the general policy.
• Follow-up implementation work remains in the linked child issues.

Related Infrastructure planning: #484.