feat(cloud-dns): DNSSEC enabled by default for public zones#393
Merged
Conversation
Adds a dnssec_enabled variable (default false) that configures dnssec_config on the managed zone. Only applies to public zones, since Cloud DNS does not support DNSSEC on private zones. Addresses Trivy alert GCP-0013 (Cloud DNS should use DNSSEC).
Zone signing is inert until the consumer publishes the DS record at the domain registrar, so existing zones keep resolving unchanged. Consumers can opt out with dnssec_enabled = false. Resolves Trivy alert GCP-0013 (Cloud DNS should use DNSSEC).
gdrojas
changed the title
agustincelentano
approved these changes
Jun 12, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
dnssec_enabledvariable (defaulttrue) to the GCP Cloud DNS module that setsdnssec_config { state = "on" }on the managed zone.dnssec_enabled = false.Effect on existing consumers
Next
applyon public zones shows an in-place update addingdnssec_config(GCP creates and manages the signing keys). No zone recreation, no downtime, no change in DNS resolution.Resolves Trivy code-scanning alert #5 (GCP-0013: Cloud DNS should use DNSSEC).
Test plan
tofu test— 9/9 pass (3 new: on by default for public zones, explicit opt-out, ignored for private zones)tofu fmt/tofu validateclean (pre-commit)🤖 Generated with Claude Code