-
Notifications
You must be signed in to change notification settings - Fork 39
Ttl cache from DNS server #14
Comments
I answer my own question. |
Until this is supported by nodejs itself (7.2?), we are not going to add such a feature to this module. Instead, the assumption is that those using this module understand the risks involved with overriding the DNS server TTL. (In most cases, the expectation is that the TTL of dnscache will be set to a smaller value than most DNS server TTLs since its primary purpose is to prevent overloading/latency of said DNS servers). |
This is now supported as of Node.js 7.2 . Here are the docs for the new feature. |
This was also backported to 6 today (6.11.0). https://github.com/nodejs/node/blob/4c5cbb7c8367abde6409ce68eee0e5eb5f07903d/doc/changelogs/CHANGELOG_V6.md#6.11.0 |
@PaquitoSoft @evantorrie @robertrossmann @SimenB Hello! I've found that this module is unsupported and has some bugs. I may propose to use our module that was tested in production and highload environments. Also we have good unit and functional tests with 100% coverage, multi-records resolving and TTL support. Here it is: https://github.com/LCMApps/dns-lookup-cache |
Hi!
Reading about the possibility to add caching capabilities to nodejs DNS module (which it seems it's not going to happen), there's a comment in this thread with a warning about dnscache module.
Here is the link to the thread.
Here is the comment:
Is there any chance for this module to respect the TTL set by the DNS server?
Thanks.
The text was updated successfully, but these errors were encountered: