Description
Version information:
0.4.18
Type:
enhancement
Description:
Historical background can be found in #1054
DNS query API at /api/v0/dns resolves FQDN to IPFS path (if DNSLink exists).
It is heavily used by ipfs-companion however we don't know for how long DNSLink (DNS TXT record) is valid and use a static cache expiration value, which has its downsides.
Ideally, we would add an opt-in --ttl flag to extend response of /api/v0/dns and use actual TTL in cache expiration logic.
A response with --ttl could look like this:
{
"Path": "/ipfs/QmS4fTD7Rh8NouNhp9uZbawUdBpgHaUTeL3EnxX8Tiiu7H",
"TTL": 60,
}
For what its worth I did a quick check and go-ipfs/namesys uses net.LookupTXT which returns strings with text, but no TTL, so I imagine standard library is not enough, and we would have to introduce more advanced DNS library to make this work.
Does this sound feasible on go-ipfs end?
What would be the next step?