You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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).
In reality, it's not a cache time, it's a periodic reset frequency:
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.
The text was updated successfully, but these errors were encountered:
fallbackDuration
is documented as:In reality, it's not a cache time, it's a periodic reset frequency:
cacheable-lookup/source/index.js
Lines 97 to 106 in da10b58
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.
The text was updated successfully, but these errors were encountered: