[GH-ISSUE #376] Smarter Cache for loading with Docker and LocalDB Solvers #127

Closed
opened 2026-02-26 04:34:08 +03:00 by kerem · 0 comments
Owner

Originally created by @mageddo on GitHub (Mar 18, 2023).
Original GitHub issue: https://github.com/mageddo/dns-proxy-server/issues/376

Introduction

After #370 DPS has a cache that increases its performance, as a drawback hostnames which aren't found are being cached for an hour, it means that a hostname not solved but later available because of a container started or created entry on localdb won't solve because it's cached for an hour.

Goals

The objective is to keep the 1 hour cache but just for records that aren't found at the remote and don't exists on localdb and docker containers.

Solution

There will be 2 caches

Remote Cache

Will cache only remote answers with longer periods as described at #370

Global Cache

It caches all solvers but for a period of 20 seconds in case of remote solvers, 30 seconds for docker containers and the specified ttl on the config file for localdb entries.

When the cache expires will try a hot load except by the remote solver which will be cached by the secondary RemoteCache

Originally created by @mageddo on GitHub (Mar 18, 2023). Original GitHub issue: https://github.com/mageddo/dns-proxy-server/issues/376 ## Introduction After #370 DPS has a cache that increases its performance, as a drawback hostnames which aren't found are being cached for an hour, it means that a hostname not solved but later available because of a container started or created entry on localdb won't solve because it's cached for an hour. ## Goals The objective is to keep the 1 hour cache but just for records that aren't found at the remote and don't exists on localdb and docker containers. ## Solution There will be 2 caches ### Remote Cache Will cache only remote answers with longer periods as described at #370 ### Global Cache It caches all solvers but for a period of 20 seconds in case of remote solvers, 30 seconds for docker containers and the specified ttl on the config file for localdb entries. When the cache expires will try a hot load except by the remote solver which will be cached by the secondary RemoteCache
kerem 2026-02-26 04:34:08 +03:00
  • closed this issue
  • added the
    feature
    label
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/dns-proxy-server-mageddo#127
No description provided.