Azure Dns Migration

What it is responsible for

Azure Dns Migration turns pams.net DNS from GoDaddy-managed records into Azure-managed DNS, then guides wildcard SSL setup for *.pams.net through cert-manager and an Azure DNS ClusterIssuer. Its quick-start flow creates an Azure DNS zone, imports records, tests before nameserver changes, verifies migration after propagation, creates a managed identity with DNS permissions, and deploys the issuer. The documented sequence stops migration when pre-switch tests fail and records the managed-identity client ID for issuer configuration.

Notable members

• Azure DNS Migration - Quick Start Guide directs GoDaddy nameserver switching, five-minute NS checks, and post-change verification.
• 2-import-records.sh imports DNS records; 5-verify-migration.sh checks whether migration succeeded.
• 4-setup-managed-identity.sh creates the cert-manager identity, grants permissions, and writes its client ID to the data file; cert-manager-azure-issuer.yaml receives the ID and is applied to deploy wildcard SSL.

319 entities in azure-dns-migration. Nothing else in this repository depends on it.

What it is made of

Its 319 entities sit in 5 files under azure-dns-migration: 314 doc comments and 5 markdown docs.

Where work enters

• Azure DNS Migration - Quick Start Guide — azure-dns-migration/QUICK_START.md:1
• Azure DNS Migration for pams.net — azure-dns-migration/README.md:1
• Azure DNS Migration Checklist — azure-dns-migration/docs/MIGRATION_CHECKLIST.md:1
• Azure DNS Migration - Rollback Plan — azure-dns-migration/docs/ROLLBACK_PLAN.md:1