[GH-ISSUE #595] Feature Request: Add "defaultDpsNetworkName" option in configuration file #197

New issue

Closed

opened 2026-02-26 04:34:21 +03:00 by kerem · 1 comment

kerem commented

2026-02-26 04:34:21 +03:00

Owner

Originally created by @defung on GitHub (Nov 6, 2024).
Original GitHub issue: https://github.com/mageddo/dns-proxy-server/issues/595

Summary & Motivation

I recently created a docker network, and all my containers that needs to be exposed to DPS will belong to this network. However, as I have many containers, I found it tedious to always add a dps.network=myDpsNetwork label to all my containers. Therefore, it would be great if we can have an option in the configuration file to always use a specific network only.

Example:

{
  ...
  "defaultDpsNetworkName": "myDpsNetwork",
  ...
}

Goals

This avoids the need to add a label to all containers, and make DPS resolve IPs using that network by default. The label should still exist, in case we want to override the default set in the configuration file.

Originally created by @defung on GitHub (Nov 6, 2024). Original GitHub issue: https://github.com/mageddo/dns-proxy-server/issues/595 ## Summary & Motivation I recently created a docker network, and all my containers that needs to be exposed to DPS will belong to this network. However, as I have many containers, I found it tedious to always add a `dps.network=myDpsNetwork` label to all my containers. Therefore, it would be great if we can have an option in the configuration file to always use a specific network only. Example: ``` { ... "defaultDpsNetworkName": "myDpsNetwork", ... } ``` ## Goals This avoids the need to add a label to all containers, and make DPS resolve IPs using that network by default. The label should still exist, in case we want to override the default set in the configuration file.

kerem

2026-02-26 04:34:21 +03:00

closed this issue
added the
feature-request
label

kerem commented

2026-02-26 04:34:22 +03:00

Author

Owner

@mageddo commented on GitHub (Dec 17, 2025):

Hey. #662 is intended to satisfy your usecase, checkout 5.3.x, I would appreciate your feedback, see the docs. Thanks in advance.

@mageddo commented on GitHub (Dec 17, 2025): Hey. #662 is intended to satisfy your usecase, checkout [5.3.x](https://github.com/mageddo/dns-proxy-server/releases/tag/5.3.0-snapshot), I would appreciate your feedback, see the [docs][1]. Thanks in advance. [1]: https://mageddo.github.io/dns-proxy-server/5.3/en/2-features/specify-from-which-network-solve-container/