fix(dnscaching): check dnsCache before init & support forceipv4 with caching (#1910)
* fix: ensure dnsCache is checked for when its enabled before initialization previously dnsCache was being initialized even if it was disabled because the previous check was always returning truthy. fix #1857 * chore: update dns-caching to 0.2.6 This will allow dns-caching to respect forceIpv4 flag. * chore: update dns-caching to 0.2.7
This commit is contained in:
@@ -57,7 +57,7 @@
|
||||
"cronstrue": "2.23.0",
|
||||
"date-fns": "2.29.3",
|
||||
"dayjs": "1.11.7",
|
||||
"dns-caching": "^0.2.5",
|
||||
"dns-caching": "^0.2.7",
|
||||
"email-templates": "12.0.1",
|
||||
"email-validator": "2.0.4",
|
||||
"express": "4.21.2",
|
||||
|
||||
536
pnpm-lock.yaml
generated
536
pnpm-lock.yaml
generated
File diff suppressed because it is too large
Load Diff
@@ -82,7 +82,7 @@ app
|
||||
}
|
||||
|
||||
// Add DNS caching
|
||||
if (settings.network.dnsCache) {
|
||||
if (settings.network.dnsCache?.enabled) {
|
||||
initializeDnsCache({
|
||||
forceMinTtl: settings.network.dnsCache.forceMinTtl,
|
||||
forceMaxTtl: settings.network.dnsCache.forceMaxTtl,
|
||||
|
||||
Reference in New Issue
Block a user