Skip to content
New issue

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

allow the dns_ns_record_set data source to query a particular nameserver #172

Open
dmildh opened this issue Oct 19, 2021 · 2 comments
Open

Comments

@dmildh
Copy link

dmildh commented Oct 19, 2021

Description

It would be useful to allow the dns_ns_record_set data source to query custom nameserver(s) of your choosing for times you need to override your client's dns configuration. For example when working on my company's vpn our dns is forced to use our local dns but the answer can only come from our corporate dns server for a internally delegate dns zone

New or Affected Resource(s)

  • dns_ns_record_set data

Potential Terraform Configuration

data "dns_ns_record_set" "domain_ns_names" {
  host = asubdomain.somedomain.com
  nameservers = ["8.8.8.8"] # custom nameserver(s) to query
}
@herrsorgenfrei
Copy link

herrsorgenfrei commented Oct 25, 2021

Currently the dns-provider can be configured using the update-block - but as the name states correctly this configuration is only taken for updates. It would be nice if you could state a query-block on the configuration that defines the nameserver to query the dns-entries from.
What do you think?

@dmildh
Copy link
Author

dmildh commented Oct 25, 2021

Currently the dns-provider can be configured using the update-block - but as the name states correctly this configuration is only taken for updates. It would be nice if you could state a query-block on the configuration that defines the nameserver to query the dns-entries from. What do you think?

Yeah that's along the lines of what I was thinking. Just needs to be queried from this name server during the stack run.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants