dns: TTL for TXT entries

[martinheidegger]

The dns.lookupTxt() function returns the TXT entries but omits the TTL entries. This is a problem if one intends to add a cache on top of lookupTxt()

Describe the solution you'd like

Probably the best I could see is to have an option for lookupTxt in the form of { ttl: true } that returns a value + ttl object instead of a simple string:

dns.lookupTxt('domain', { ttl: true }, (err, data) => {
  data[0].value // text entry
  data[0].ttl // ttl number
})

[evanlucas]

It doesn't look like cares supports this out of the box. c-ares/c-ares#393 seems to be some progress though.

I did find a patch thanks to @saghul's work on https://github.com/saghul/pycares that adds TTL support to cares, but it breaks ABI

[richardlau]

#14713 is the Node.js issue tracking things "missing" from c-ares.

[targos]

Also, #38184 could be the solution to many of these :)

[tniessen]

Just copying #39528 (comment) from a duplicate issue:

For reference, the ttl option was discussed in #5893 and added in #9296.

The implementation appears to achieve this using ares_parse_a_reply and ares_parse_aaaa_reply, respectively. However, other parse functions, such as ares_parse_ns_reply, ares_parse_ptr_reply, ares_parse_mx_reply, ares_parse_txt_reply_ext, etc. do not appear to support retrieving the TTL of the records.

[github-actions]

There has been no activity on this feature request for 5 months and it is unlikely to be implemented. It will be closed 6 months after the last non-automated comment.

For more information on how the project manages feature requests, please consult the feature request management document.

[github-actions]

There has been no activity on this feature request and it is being closed. If you feel closing this issue is not the right thing to do, please leave a comment.

For more information on how the project manages feature requests, please consult the feature request management document.