Azure Private DNS Zone
A self-contained Azure Private DNS zone with virtual-network links and optional record sets for private name resolution across VNets and Private Endpoints - VM auto-registration off by default.
Verification
Live-testedReally deployed to a cloud sandbox, verified against its outputs and assertions, then destroyed - with the teardown confirmed.
Conformance
- Static validation (fmt · validate · tflint)
- Security scan clean (Checkov)
- Plan test superseded by live test
Provenance
- SHA-256 checksum
- Cosign signature
Functional
- Live-tested - applied, verified, destroyed
Last verified 2026-06-30 · how we verify
Verify this download
cosign · sha-256Don't take our word for it. Every release is signed with cosign - check the bytes against our pinned public key before you trust them.
# 1. Our pinned public key - fetch once, trust out-of-band
curl -O https://www.iac-bazaar.com/cosign.pub
# 2. This module's Sigstore bundle
curl -o azure-private-dns-1.0.0.sigstore.json \
https://www.iac-bazaar.com/api/artifacts/azure-private-dns/signature
# 3. Verify the tarball you downloaded
cosign verify-blob \
--key cosign.pub \
--bundle azure-private-dns-1.0.0.sigstore.json \
azure-private-dns-1.0.0.tar.gz
# → Verified OK
# 4. (optional) confirm the checksum too
echo "8cacc984c2426ecdf3db828a0b8425485deffb2f803090a2e212f590d8a4b931 azure-private-dns-1.0.0.tar.gz" | sha256sum -cUse it from the registry
terraform · opentofumodule "private_dns" {
source = "www.iac-bazaar.com/iac-bazaar/azure-private-dns/azure"
version = "1.0.0"
}Needs a registry token from /account/tokens. The module itself is free; the account is what identifies you. Full setup: registry docs.
Cite it in your README
badge · attributionPaste this beside the module in the repository that uses it. The badge is rendered from this artifact's verification record, so it reads live-tested because the record says so, and the link lands on this page.
[](https://www.iac-bazaar.com/catalog/azure-private-dns?utm_source=syndication&utm_medium=readme&utm_campaign=artifact)
Terraform module 1.0.0, live-tested on IaC Bazaar: [Azure Private DNS Zone](https://www.iac-bazaar.com/catalog/azure-private-dns?utm_source=syndication&utm_medium=readme&utm_campaign=artifact)
```hcl
module "private_dns" {
source = "www.iac-bazaar.com/iac-bazaar/azure-private-dns/azure"
version = "1.0.0"
}
```Preview:
Inputs & outputs
Create a free account to read this module's contract
The declared contract - every input name, type, default and description, plus every output - is shown to signed-in accounts, not to anonymous visitors.
A free account sees the contract of every module in the catalogue. There is no subscription and nothing to buy - the modules are free to download, and they run under Vizier.
Documentation
azure-private-dns
Azure Private DNS zone with virtual-network links and optional record sets —
private name resolution for VNets, Private Endpoints and split-horizon internal
domains, done right. The module is self-contained: by default it creates its
own resource group and a virtual network, the private DNS zone, the zone⇄VNet
link, and any A/CNAME records you declare. One tofu apply yields a resolvable
private zone; tofu destroy removes everything (including the resource group).
Secure by default: private DNS zones are inherently private (resolvable only from
linked VNets, never the public internet), and VM auto-registration
(registration_enabled) is off unless you opt in per link. Works with
Terraform and OpenTofu (>= 1.6), azurerm provider >= 4.0, < 5.0.
Security notes
- Private DNS zones are not internet-resolvable — there is no public-access flag to harden. Records are visible only to VNets explicitly linked here.
- Keep
registration_enabled = falseunless you need VM auto-registration. Azure permits auto-registration on at most one linked VNet per zone; the module does not stop you from enabling it on several, but the apply will fail. - For Private Endpoint integration, name the zone after the service's privatelink
domain (e.g.
privatelink.blob.core.windows.net) and link the consuming VNets. - The module owns its resource group, so
destroyis clean and leaves nothing behind.
Requirements
| Requirement | Version |
|---|---|
| Terraform / OpenTofu | >= 1.6 |
hashicorp/azurerm | >= 4.0, < 5.0 |
License
Commercial — IaC Bazaar EULA. © IaC Bazaar. Original work (not derived from a third-party module).
Usage code & full reference need an account
The complete copy-paste usage, the full input/output reference, and operational notes are free with an account - shown here and bundled in the download. Sign in and this section fills in.
- Usage
- Inputs
- Outputs
Related modules
azure-dns-private-resolver
A resolver is five resources - endpoints, ruleset, rules and VNet links - and the half-built state most sit in resolves Azure names and forwards nothing to on-premises; a ruleset not linked to a VNet applies to nothing; and each endpoint needs its own delegated subnet. All five created, forwarding rules required, VNet links expected (none by name), the inbound address exported.
azure-dns-zone
An Azure public DNS zone plus a map-driven set of record sets - A, AAAA, CNAME, TXT, MX, NS, CAA and SRV - with relative naming, verbatim TXT values, and apex footgun guards.
civo-dns-zone
A Civo DNS zone with every record in one map, each with the TTL Civo requires per record, and the nameservers exported for the registrar. Civo does not sign zones and has no CAA or NS record types; dnssec_available says so, so a domain that needs DNSSEC is sent elsewhere before it is delegated.
do-dns-zone
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.
tencent-dns-zone
A Tencent Cloud DNSPod zone with every record in one map, all on the default resolution line so every resolver gets the same answer, MX priority carried on the record, and the free-grade nameservers exported for the registrar. DNSSEC is not a resource in the provider; dnssec_available says so.
huawei-dns-zone
A Huawei Cloud public DNS zone with the flat record map grouped into the record sets Huawei expects (one per name and type, several values), DNSSEC on with the DS record for the registrar, and the nameservers exported. Private zones bound to a VPC are a different zone type and not this module.