mirror of
https://github.com/mageddo/dns-proxy-server.git
synced 2026-04-25 17:35:54 +03:00
[GH-ISSUE #248] systemd-resolved integration #102
Labels
No labels
bug
confirmed
discussion
duplicate
enhancement
feature
feature-request
not-planned
pull-request
secondary-feature
stale
triage
waiting-feedback
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/dns-proxy-server-mageddo#102
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @sh3bang on GitHub (Oct 6, 2022).
Original GitHub issue: https://github.com/mageddo/dns-proxy-server/issues/248
Hello,
first of all: DPS is a very helpful Service, thank you very much!
I can understand to replace the /etc/resolv.conf file, it is the most common way to use a different DNS Server. But with systemd-resolved on the Host it isn't recommend. systemd-resolved offer a API to change or add DNS Servers. Therefore i ask to integrate systemd-resolved instead of replacing system files.
@SimJoSt commented on GitHub (Dec 2, 2022):
Duplicate: https://github.com/mageddo/dns-proxy-server/issues/246
@mageddo commented on GitHub (Feb 23, 2023):
Hey, thank your for the feedback @sh3bang .
I wouldn't know about this systemd-resolved ability to change the DNS servers, I think it would be a nice feature, I will take a look to understand how to use it, probably won't be a problem when running locally but asking myself if it will be possible to use that when DPS is running inside a container.
@sh3bang commented on GitHub (Feb 23, 2023):
The mistake is to replace /etc/resolv.conf by DPS Container. Keep it as-is and add a custom DNS server (DPS on top of all other in the resolver list), e.g. by adding the container IP to /etc/systemd/resolved.conf
Or just have a look at "adguard"
@mageddo commented on GitHub (Feb 25, 2023):
Hey @sh3bang I've made some tests with systemd-resolved and reported them on this thread, when using it correctly docker behavior gets a lot better, but I've noticed that won't to able to automatically configure system-resolved when DPS is running inside a container as I expected because systemd-resolved restart is required.
Do you know any workaround?
@mageddo commented on GitHub (Feb 25, 2023):
I consolidated the feature specs at https://github.com/mageddo/dns-proxy-server/issues/321
@mageddo commented on GitHub (Feb 26, 2023):
The feature is alive at DPS 3.4, please check it out and give me a feedback if possible. See #321 for some instructions of how to use it, I will update the docs later.
I'm using the following command:
@sh3bang commented on GitHub (Oct 13, 2023):
@mageddo Thanks, DPSis now working fine with systemd-resolved!