Demo

This guide walks through a complete DNS exercise on F5 Distributed Cloud, driven by Terraform. It is structured as four phases that a human operator or an AI assistant can run end-to-end. Each phase is idempotent: rerunning it converges to the same state.

Exercise phases

Phase	Goal
Phase 1 — Build	Deploy the primary DNS zone with Terraform; wire remote state and CI
Phase 2 — Validate	Confirm the zone resolves on the public internet and the plan is idempotent
Phase 3 — Failover	Add a DNS load balancer with health-checked failover (pending the DNS-LB module)
Phase 4 — Teardown	Destroy the managed objects after explicit confirmation

Prerequisites

• Terraform ≥ 1.5.
• The f5-sales-demo/xcsh provider ≥ 3.62.0 (system-only namespaces default automatically), resolved from the Terraform registry — or a local build via dev_overrides.
• An F5 XC API token with access to the system namespace.
• The Azure CLI, signed in with Contributor on the subscription, for the one-time state backend bootstrap.

Caution

The domain used here is delegated to F5 XC, so records you create resolve on the public internet. Use a domain you own and intend to manage — the plan is variable-driven precisely so you can target your own.

Start with Phase 1 — Build.