-
-
Notifications
You must be signed in to change notification settings - Fork 37.2k
dns: TTL for TXT entries #39399
Copy link
Copy link
Closed
Labels
caresIssues and PRs related to the c-ares dependency or the cares_wrap binding.Issues and PRs related to the c-ares dependency or the cares_wrap binding.dnsIssues and PRs related to the dns subsystem.Issues and PRs related to the dns subsystem.feature requestIssues requesting new Node.js features.Issues requesting new Node.js features.staleIssues and PRs marked stale due to inactivity and scheduled for automatic closure.Issues and PRs marked stale due to inactivity and scheduled for automatic closure.
Description
Activity
Metadata
Metadata
Assignees
Labels
caresIssues and PRs related to the c-ares dependency or the cares_wrap binding.Issues and PRs related to the c-ares dependency or the cares_wrap binding.dnsIssues and PRs related to the dns subsystem.Issues and PRs related to the dns subsystem.feature requestIssues requesting new Node.js features.Issues requesting new Node.js features.staleIssues and PRs marked stale due to inactivity and scheduled for automatic closure.Issues and PRs marked stale due to inactivity and scheduled for automatic closure.
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 oflookupTxt()Describe the solution you'd like
Probably the best I could see is to have an option for
lookupTxtin the form of{ ttl: true }that returns a value + ttl object instead of a simple string: