A DNS Zone, and a Plain Account of Why It Is Not Yet Serving Anybody
A DigitalOcean domain and its records. Creating the zone does not delegate it: until the registrar's nameservers point here the zone is correct, complete and serving nobody, which looks exactly like a working zone. The domain's ip_address shortcut, which hides an apex A record from your records map, is deliberately not used, and a CNAME at the apex is refused.
This is the operations reference: version drift, dependants and neighbours. For what the module provisions, its inputs and outputs, and how to buy it, see the catalogue entry.
Provider drift
This artifact declares no Terraform provider requirements, so there is nothing to drift. Provider freshness applies to Terraform and OpenTofu modules.
What depends on this
No reference architecture names this module, so changing it affects only configurations that reference it directly.
Nearest alternatives
Nothing else in the catalogue covers dns on DigitalOcean. If this module is not the right shape, the closest options are on other clouds.
The same job on other clouds
DNS & Traffic Management on other providers. Useful when the cloud is still open, or when you are pricing a second one. How far a comparison like that can be trusted is covered in comparing clouds.
Installing it
module "do_dns_zone" {
source = "www.iac-bazaar.com/iac-bazaar/do-dns-zone/digitalocean"
version = "1.0.0"
}A registry token is required for the download itself. Installing through the registry protocol has the two credential steps.