[GH-ISSUE #582] Feature Request: Use resolv.conf instead of systemd-resolved when running inside docker container #191

New issue

Closed

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

kerem commented

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

Owner

Originally created by @mageddo on GitHub (Sep 30, 2024).
Original GitHub issue: https://github.com/mageddo/dns-proxy-server/issues/582

Summary & Motivation

To prevent cases like #580 , maybe it would make sense to DPS edit resolv.conf file instead of system resolved file even when it is on the first place at the priority because DPS won´t be able to configure itself automatically as the default DNS when inside docker container.

Drawbacks:

That's an deliberated decision did by DPS, will that decision be unwated in some usecase?

Example:

Provide a solver which can solve from previously configured DNS records.
It's will be useful because people can use DPS for static DNS entries instead of use /etc/hosts or something like.

Goals

What is supposed to do in short. (Optional)

Example

A simple, static DNS server

Non-Goals

What people would think it is supposed to do, but it is not? (Optional)

Example

Not to implement a full and complex DNS server

Description

Explain the feature details and how it would work, usecases, examples, snippets of code,
inputs and outputs, etc. (Required)

Example

Storage

DNS records will be stored at the existing DPS config file.

DNS Records

It will have support to A, AAAA and CNAME entries.

Also, TTL by record will be supported

Originally created by @mageddo on GitHub (Sep 30, 2024). Original GitHub issue: https://github.com/mageddo/dns-proxy-server/issues/582 ## Summary & Motivation To prevent cases like #580 , maybe it would make sense to DPS edit resolv.conf file instead of system resolved file even when it is on the first place at the priority because DPS won´t be able to configure itself automatically as the default DNS when inside docker container. Drawbacks: * That's an deliberated decision did by DPS, will that decision be unwated in some usecase? Example: > Provide a solver which can solve from previously configured DNS records. > It's will be useful because people can use DPS for static DNS entries instead of use /etc/hosts or something like. ## Goals > What is supposed to do in short. (Optional) Example > A simple, static DNS server ## Non-Goals > What people would think it is supposed to do, but it is not? (Optional) Example > * Not to implement a full and complex DNS server ## Description > Explain the feature details and how it would work, usecases, examples, snippets of code, > inputs and outputs, etc. (Required) Example > ### Storage > > DNS records will be stored at the existing DPS config file. > > ### DNS Records > * It will have support to A, AAAA and CNAME entries. > * Also, TTL by record will be supported