I looked into invalidating the cache on error from @zeit/fetch but even doing that would require changes afaict, because the call to resolve doesn't take any options. This seemed like a more straightforward fix, and it still allows for users of this lib to specify a higher minimum, while working OOTB for a greater number of DNS configurations (ie, it will work for those that have 60s TTL like AWS ELBs).
sandinmyjoints
commented
4 years ago
Fixes https://github.com/zeit/fetch/issues/35
I looked into invalidating the cache on error from @zeit/fetch but even doing that would require changes afaict, because the call to resolve doesn't take any options. This seemed like a more straightforward fix, and it still allows for users of this lib to specify a higher minimum, while working OOTB for a greater number of DNS configurations (ie, it will work for those that have 60s TTL like AWS ELBs).