chrisryn/requestarr
1
0
Fork 0
Code Issues Pull Requests Actions 5 Packages Projects Releases Wiki Activity

fix(dnscaching): check dnsCache before init & support forceipv4 with caching (#1910)

Browse Source 
* 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:
fallenbagel
2025-09-18 16:30:42 +05:00
committed by GitHub
parent cd479d0d17
commit 9e737576de
3 changed files with 280 additions and 260 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
package.json
View File

@@ -57,7 +57,7 @@
"cronstrue": "2.23.0", "cronstrue": "2.23.0",
"date-fns": "2.29.3", "date-fns": "2.29.3",
"dayjs": "1.11.7", "dayjs": "1.11.7",
"dns-caching": "^0.2.5", "dns-caching": "^0.2.7",
"email-templates": "12.0.1", "email-templates": "12.0.1",
"email-validator": "2.0.4", "email-validator": "2.0.4",
"express": "4.21.2", "express": "4.21.2",

536
pnpm-lock.yaml generated
View File

File diff suppressed because it is too large Load Diff

2
server/index.ts
View File

@@ -82,7 +82,7 @@ app
} }
// Add DNS caching // Add DNS caching
if (settings.network.dnsCache) { if (settings.network.dnsCache?.enabled) {
initializeDnsCache({ initializeDnsCache({
forceMinTtl: settings.network.dnsCache.forceMinTtl, forceMinTtl: settings.network.dnsCache.forceMinTtl,
forceMaxTtl: settings.network.dnsCache.forceMaxTtl, forceMaxTtl: settings.network.dnsCache.forceMaxTtl,