A Vultr DNS Zone with Its Records, Signed, and the Nameservers for the Registrar
A Vultr DNS zone with every record in one map, DNSSEC on (the DS record still has to go to the registrar), and the nameservers exported because the zone answers nothing until the registrar delegates to them. The apex A record Vultr offers to write at creation is not used, so nothing exists outside the map.
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 Vultr. 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 "vultr_dns_zone" {
source = "www.iac-bazaar.com/iac-bazaar/vultr-dns-zone/vultr"
version = "1.0.0"
}A registry token is required for the download itself. Installing through the registry protocol has the two credential steps.