node:dns resolver ignores TTL option

[slagiewka]

Version: Deno 2.1.5

import {resolve4} from "node:dns/promises";

resolve4("deno.com", {ttl: true}).then(console.log);

Expected result:

[{ address: '34.120.54.55', ttl: 12345 }]

Actual result:

[ "34.120.54.55" ]

Deno docs are aware of possible object being returned: https://docs.deno.com/api/node/dns/promises/~/resolve4

Node docs specify the behaviour for ttl: true: https://nodejs.org/api/dns.html#dnspromisesresolve4hostname-options

It makes cacheable-lookup fail because the library sets the option and expects the object to be returned:

error: Uncaught TypeError: Cannot create property 'family' on string '34.120.54.55'
    at CacheableLookup._resolve (file:///my_home/node_modules/cacheable-lookup/source/index.js:264:20)
    at eventLoopTick (ext:core/01_core.js:175:7)
    at async CacheableLookup.queryAndCache (file:///my_home/node_modules/cacheable-lookup/source/index.js:347:17)
    at async CacheableLookup.query (file:///my_home/node_modules/cacheable-lookup/source/index.js:235:20)
    at async CacheableLookup.lookupAsync (file:///my_home/node_modules/cacheable-lookup/source/index.js:178:18)

[siaeyy]

In op_dns_resolve, we only deal with record data (Format). So we can not deal with ttl values, in both node:dns and Deno.resolveDns. I think some basis things in operations module should be changed.