You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
}
The text was updated successfully, but these errors were encountered:
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?
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.
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)
Potential Terraform Configuration
The text was updated successfully, but these errors were encountered: