Use the data source to retrieve the following information for a TXT record, which is managed by a NIOS server:
Parameter | Description | Example |
|---|---|---|
| The DNS view in which the record's zone exists. |
|
| The fully qualified domain name to which a textual value is assigned. |
|
| The textual value for the TXT record. |
test.com
| ||
| The zone that contains the record. |
|
| The Time to Live value of the record, in seconds. |
|
| A description of the record. This is a regular comment. |
|
| The set of extensible attributes of the record, if any. The content is formatted as a string of JSON map. |
|
To get retrieve information about a TXT record, specify the FQDN of the domain to which the text record is assigned, the FQDN of the mail exchange host, and the preference numberTXT records that match the specified filters, use the filters argument and specify the parameters mentioned in the below table. These are the searchable parameters of the corresponding object in Infoblox NIOS WAPI. If you do not specify any parameter, the data source retrieves information about all TXT records in the NIOS Grid.
The following table describes the parameters you can define in an infoblox_txt_record data source block:
Parameter |
|---|
Alias* | Description |
|---|---|
|
|
Specifies the fully qualified domain name to which the textual value is assigned. | ||
|
| Specifies the textual value for the TXT record. |
|
|
Specifies the DNS view in which the record’s zone exists. |
default will be used as the DNS view name.If the zone is in a non-default DNS view, then you must specify that view
matching objects are retrieved from all DNS views in the NIOS Grid. | ||
|
| Specifies the zone that contains the record. |
|
| Describes the record. |
Extensible Attributes | - | Specifies the extensible attributes specified for the record. You must specify the key/value pair within the |
*Aliases are the parameter names used in the prior releases of Infoblox IPAM Plug-In for Terraform. Do not use the alias names for parameters in the data source blocks. Using them can result in error scenarios.
Example of the TXT Record Data Source Block
...
resource "infoblox_txt_record" "rec3" { dns_view = "nondefault_dnsview1" fqdn = "example3.example2.org" text = "\"data for TXT-record #3\"" ttl = 300 comment = "example TXT record #3" ext_attrs = jsonencode({ "Location" = "65.8665701230204, -37.00791763398113" })}
data "infoblox_txt_record" "ds3" { filters = { dns_ view = "nondefault_dnsview1" fqdn name = "example3.example2.org" text = "\"data for TXT-record #3\"" } // This is just to ensure that the record has been be created // using 'infoblox_txt_record' resource block before the data source will be queried. depends_on = [infoblox_txt_record.rec3]}
output "txt_rec3rec_textres" { value = data.infoblox_txt_record.ds3.text}
// accessing individual field in resultsoutput "txt_rec3rec_zonemes" { value = data.infoblox_txt_record.ds3.zone}output "txt_rec3_ttl" { value = data.results.0.text //zero represents index of json object from results list}
// Searching for TXT-Record by specifying EAsdata "infoblox_txt_record.ds3.ttl}output " "txt_rec3rec_commentea" { value = data.infoblox_txt_record.ds3.comment} filters = { "*Location" = "65.8665701230204, -37.00791763398113" "*Location!" = "75.8665701230211" }}
// throws matching TXT-Records with EA, if anyoutput "txt_rec3rec_ext_attrsout" { value = data.infoblox_txt_record.ds3.ext_attrstxt_rec_ea}