When the DNS server responds with ENOTFOUND or ENODATA and the OS reports that the entry is available, it will use dns.lookup(...) directly for the requested hostnames for the specified amount of time (in seconds).
For example, if it's set to 1 hour, and then 55 minutes after creating the CacheableLookup instance a hostname lookup fails, the fallback usage will only be cached for 5 minutes (the time until the next reset).
This isn't a big problem for me particularly right now, just something I noticed.
fallbackDuration
is documented as:In reality, it's not a cache time, it's a periodic reset frequency: https://github.com/szmarczak/cacheable-lookup/blob/da10b58475ab89e944ec112f521e86402c344fc1/source/index.js#L97-L106
For example, if it's set to 1 hour, and then 55 minutes after creating the CacheableLookup instance a hostname lookup fails, the fallback usage will only be cached for 5 minutes (the time until the next reset).
This isn't a big problem for me particularly right now, just something I noticed.