Linode DNS Zone & Records
Complete DNS zone with typed record management and sane TTL defaults on Linode's free DNS Manager.
Verification
Static-verifiedPassed: validated and lint-clean (provider-schema-validated for AWS/Azure/GCP; Terraform-language lint elsewhere).
Conformance
- Static validation (fmt · validate · tflint)
- Security scan clean (Checkov)
- Plan tests (mocked: validation rules · outputs)
Provenance
- SHA-256 checksum
- Cosign signature
Functional
- Live test pending (no cloud run yet)
Last verified 2026-06-28 · 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 linode-domain-1.0.0.sigstore.json \
https://www.iac-bazaar.com/api/artifacts/linode-domain/signature
# 3. Verify the tarball you downloaded
cosign verify-blob \
--key cosign.pub \
--bundle linode-domain-1.0.0.sigstore.json \
linode-domain-1.0.0.tar.gz
# → Verified OK
# 4. (optional) confirm the checksum too
echo "7bd669483153ea7fcc89b021e76e94f3c9426e72928b286d88cb05720ca255f5 linode-domain-1.0.0.tar.gz" | sha256sum -cUse it from the registry
terraform · opentofumodule "domain" {
source = "www.iac-bazaar.com/iac-bazaar/linode-domain/linode"
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 static-verified because the record says so, and the link lands on this page.
[](https://www.iac-bazaar.com/catalog/linode-domain?utm_source=syndication&utm_medium=readme&utm_campaign=artifact)
Terraform module 1.0.0, static-verified on IaC Bazaar: [Linode DNS Zone & Records](https://www.iac-bazaar.com/catalog/linode-domain?utm_source=syndication&utm_medium=readme&utm_campaign=artifact)
```hcl
module "domain" {
source = "www.iac-bazaar.com/iac-bazaar/linode-domain/linode"
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
linode-domain
Complete Linode DNS zone (DNS Manager) with typed, declarative record
management and sane TTL defaults. Master (authoritative) or slave (AXFR
mirror) zones. Works with Terraform and OpenTofu (>= 1.6), Linode
provider >= 3.14, < 4.0.
Status: static-validated, live-test pending. This module ships under live-test quarantine: it has passed
tofu fmt,tofu validate, andtflint, but the real apply → verify → destroy gate is pending a Linode sandbox account. Treat the secure defaults below as the contract.
Design & secure defaults
- One declarative
recordsmap. Every record is a typed object validated at plan time —record_typeis constrained to the supported set, CAA records must carry a validtag, and SRV records must supplyservice,protocol, andport. No stringly-typed footguns. - AXFR closed by default.
axfr_ipsis empty unless you explicitly run secondary nameservers — open zone transfer leaks your entire zone to anyone, so the module never opens it for you. - Master/slave correctness enforced. A master zone must declare
soa_email; a slave zone must declaremaster_ips. Both are checked with plan-time preconditions, not discovered at apply. - CAA encouraged. The example pins certificate issuance to a single CA via a CAA record — a cheap, high-value control most zones omit.
- Sane TTLs. Zone and per-record TTLs default to 3600s; Linode rounds to its supported steps. The module surfaces Linode's authoritative nameservers as an output so you can complete delegation at your registrar.
Requirements
- Terraform or OpenTofu
>= 1.6 linode/linodeprovider>= 3.14, < 4.0- DNS Manager is free, but Linode only serves a zone while the account has
at least one active Linode service. Delegate the domain at your registrar to
the
nameserversoutput.
License
Commercial — LicenseRef-IaCBazaar-Commercial. © 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
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.
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.
ibm-dns-zone
An IBM Cloud DNS Services private zone, its permitted networks and its records. The zone and the permission are separate resources: with none, the zone is created, the records are created, everything reports Active, and no VPC can resolve any of it. An empty list is refused. This is private DNS and it is not the public zone, which is CIS.