We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Terraform v1.5.5 on linux_amd64
I have both development and production DNS servers. They are all primaries.
I would like to be able to give a list of DNS servers like this in the provider config:
provider "dns" { update { server = ["192.168.1.10", "192.168.2.10", "192.168.3.10"] port = "5353" key_name = "tsig-key." key_algorithm = "hmac-sha256" key_secret = var.tsig_key } }
Such that they can each receive the updated records
As above in the problem statement
High
High because if you have a multiple master setup, you cannot keep the records consistent
The text was updated successfully, but these errors were encountered:
Hi @grmhay 👋
Thank you for submitting this feature request.
We will leave this issue open and prioritise looking into this further on the basis of the level of community interest signified by up-votes.
Sorry, something went wrong.
No branches or pull requests
Terraform CLI and Provider Versions
Terraform v1.5.5
on linux_amd64
Use Cases or Problem Statement
I have both development and production DNS servers. They are all primaries.
I would like to be able to give a list of DNS servers like this in the provider config:
provider "dns" {
update {
server = ["192.168.1.10", "192.168.2.10", "192.168.3.10"]
port = "5353"
key_name = "tsig-key."
key_algorithm = "hmac-sha256"
key_secret = var.tsig_key
}
}
Such that they can each receive the updated records
Proposal
As above in the problem statement
How much impact is this issue causing?
High
Additional Information
High because if you have a multiple master setup, you cannot keep the records consistent
Code of Conduct
The text was updated successfully, but these errors were encountered: