Specify resolver to resolve requests

[Tiino1]

Terraform CLI and Provider Versions

hashicorp/dns: 3.4.2
terraform: 1.9.8

Use Cases or Problem Statement

When testing DNS setups and debugging DNS issues, it is common to have a look at what a resolver sees.
I wish I could have an equivalent of dig @resolver.server.name.or.ip domain.name.com

Proposal

I would like to specify which resolver to use inside the provider block

provider "dns" {
  resolver = "1.1.1.1"
  alias = "cloudflare"
}
provider "dns" {
  resolver = "my.resolver.domain.name.com"
  alias = "my-resolver"
}

How much impact is this issue causing?

High

Additional Information

Without this feature, I need to create an external block, invoke dig command, make sure dig is installed ... So I prefer to not use terraform at all for DNS setups as long as this feature is not available.

Code of Conduct

• I agree to follow this project's Code of Conduct

[ansgarm]

Hi @Tiino1 👋

Thank you for raising this!

Could you maybe share a bit more detail about your exact use-case for this feature?

[jdoetsch-built]

Hi @Tiino1 👋

Thank you for raising this!

Could you maybe share a bit more detail about your exact use-case for this feature?

This would be helpful for us in the case where we use a split tunnel VPN like Twingate that uses NextDNS. Twingate leverages DNS to re-route requests to Twingate-controlled servers.
So if I'm using a resource like dns_a_record_set targeting a Twingate-controlled resource and I run a Terraform plan from my local machine then the actual public DNS record doesn't get pulled but the Twingate NextDNS one does. You can imagine what kind of headache this can and has caused.

So being able to specify a specific resolver would enable me to be connected to my split tunnel VPN system and run a terraform plan at the same time.