starred/dns-proxy-server-mageddo
1
0
Fork 0
mirror of https://github.com/mageddo/dns-proxy-server.git synced 2026-04-25 09:25:56 +03:00
Code Issues 10 Projects Releases 10 Packages Wiki Activity

[GH-ISSUE #580] Bug: systemd-resolved issues #192

New issue
Closed
opened 2026-02-26 04:34:20 +03:00 by kerem · 14 comments
kerem commented 2026-02-26 04:34:20 +03:00
Owner
Copy link

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

What is Happening

starting dns-proxy from within a compose file, like:

services:
  dns-proxy:
    image: defreitas/dns-proxy-server
    hostname: dns
    volumes:
      - type: bind
        source: /var/run/docker.sock
        target: /var/run/docker.sock
      - type: bind
        source: /etc
        target: /host/etc
    ports:
      - "5380:5380"

ping dns executed from the host says Name or service not known
The logs, in addition contain the entry: Not possible to restart resolved service: service systemd-resolved restart

Actually, the command service is not present on my machine. Only systemctl restart systemd-resolved works.
However, even if I restart resolved manually, DNS lookup does not work through dns-proxy.

What is Expected

systemd-resolved is restarted and DNS lookup works.

Specs

  • Docker Version: docker version 27.1.2
  • DPS Version:
    • When using docker: the docker image version or run the following if you are using the latest docker run --rm defreitas/dns-proxy-server --version 3.25.10-snapshot
  • OS: Linux mymachine 6.10.6-10-MANJARO 1 SMP PREEMPT_DYNAMIC Sat Aug 24 16:17:40 UTC 2024 x86_64 GNU/Linux
  • Attach DPS Log file
12:03:31.664 [main           ] DEB c.m.d.config.dataprovider.ConfigPathBuilder       l=37   m=build                           status=configPathBuilt, path=/app/conf/config.json
12:03:31.675 [main           ] INF c.m.dnsproxyserver.config.dataprovider.JsonConfigsl=69   m=createDefaultConfigOnPath       status=createdDefaultConfigFile, path=/app/conf/config.json
12:03:31.676 [main           ] DEB c.m.d.config.dataprovider.ConfigDAOJson           l=32   m=find                            configPath=/app/conf/config.json
12:03:31.698 [main           ] INF c.m.d.s.d.a.DpsDockerEnvironmentSetupService      l=32   m=setup                           status=binding-docker-events, connectedToDocker=true
12:03:31.698 [main           ] INF c.m.d.s.d.a.DpsDockerEnvironmentSetupService      l=44   m=setupNetwork                    status=dpsNetwork, active=false
12:03:31.698 [main           ] INF c.m.d.s.docker.application.DpsContainerService    l=116  m=tRunningContainersToDpsNetwork  status=autoConnectDpsNetworkDisabled, dpsNetwork=false, dpsNetworkAutoConnect=false
12:03:31.698 [main           ] INF c.m.d.solver.docker.entrypoint.EventListener      l=32   m=onStart                         status=containerAutoConnectToDpsNetworkDisabled
12:03:31.698 [main           ] INF com.mageddo.dnsserver.UDPServerPool               l=31   m=start                           Starting UDP server, addresses=/0.0.0.0:53
12:03:31.698 [main           ] INF c.mageddo.dnsproxyserver.server.dns.ServerStarter l=30   m=start                           status=startingDnsServer, protocol=UDP_TCP, port=53
12:03:31.701 [virtual-44     ] INF com.mageddo.dnsserver.TCPServer                   l=56   m=start0                          status=tcpServerStarting, port=53
12:03:31.706 [main           ] INF com.mageddo.http.WebServer                        l=134  m=start                           status=startingWebServer, port=5380
12:03:36.733 [Thread-3       ] INF c.m.d.dnsconfigurator.DnsConfigurators            l=113  m=getInstance0                    usingDnsConfigurator=DnsConfiguratorLinux
12:03:36.733 [Thread-3       ] INF c.m.d.dnsconfigurator.linux.DnsConfiguratorLinux  l=122  m=init                            status=using, configFile=ResolvFile(path=/host/etc/systemd/resolved.conf, type=SYSTEMD_RESOLVED)
12:03:36.738 [Thread-3       ] WAR c.m.d.dnsconfigurator.linux.DnsConfiguratorLinux  l=145  m=tryRestartResolved              status=can't restart resolved service, please run: 'service systemd-resolved restart' to apply DPS as default DNS.
Not possible to restart resolved service: 1 : systemd-resolved: unrecognized service
Originally created by @ratcashdev on GitHub (Sep 30, 2024). Original GitHub issue: https://github.com/mageddo/dns-proxy-server/issues/580 ## What is Happening starting dns-proxy from within a compose file, like: ``` services: dns-proxy: image: defreitas/dns-proxy-server hostname: dns volumes: - type: bind source: /var/run/docker.sock target: /var/run/docker.sock - type: bind source: /etc target: /host/etc ports: - "5380:5380" ``` `ping dns` executed from the host says `Name or service not known` The logs, in addition contain the entry: `Not possible to restart resolved service: service systemd-resolved restart` Actually, the command `service` is not present on my machine. Only `systemctl restart systemd-resolved` works. However, even if I restart `resolved` manually, DNS lookup does not work through dns-proxy. ## What is Expected systemd-resolved is restarted and DNS lookup works. ## Specs * Docker Version: `docker version` 27.1.2 * DPS Version: * When using docker: the docker image version or run the following if you are using the latest `docker run --rm defreitas/dns-proxy-server --version` 3.25.10-snapshot * OS: Linux mymachine 6.10.6-10-MANJARO 1 SMP PREEMPT_DYNAMIC Sat Aug 24 16:17:40 UTC 2024 x86_64 GNU/Linux * Attach DPS Log file ``` 12:03:31.664 [main ] DEB c.m.d.config.dataprovider.ConfigPathBuilder l=37 m=build status=configPathBuilt, path=/app/conf/config.json 12:03:31.675 [main ] INF c.m.dnsproxyserver.config.dataprovider.JsonConfigsl=69 m=createDefaultConfigOnPath status=createdDefaultConfigFile, path=/app/conf/config.json 12:03:31.676 [main ] DEB c.m.d.config.dataprovider.ConfigDAOJson l=32 m=find configPath=/app/conf/config.json 12:03:31.698 [main ] INF c.m.d.s.d.a.DpsDockerEnvironmentSetupService l=32 m=setup status=binding-docker-events, connectedToDocker=true 12:03:31.698 [main ] INF c.m.d.s.d.a.DpsDockerEnvironmentSetupService l=44 m=setupNetwork status=dpsNetwork, active=false 12:03:31.698 [main ] INF c.m.d.s.docker.application.DpsContainerService l=116 m=tRunningContainersToDpsNetwork status=autoConnectDpsNetworkDisabled, dpsNetwork=false, dpsNetworkAutoConnect=false 12:03:31.698 [main ] INF c.m.d.solver.docker.entrypoint.EventListener l=32 m=onStart status=containerAutoConnectToDpsNetworkDisabled 12:03:31.698 [main ] INF com.mageddo.dnsserver.UDPServerPool l=31 m=start Starting UDP server, addresses=/0.0.0.0:53 12:03:31.698 [main ] INF c.mageddo.dnsproxyserver.server.dns.ServerStarter l=30 m=start status=startingDnsServer, protocol=UDP_TCP, port=53 12:03:31.701 [virtual-44 ] INF com.mageddo.dnsserver.TCPServer l=56 m=start0 status=tcpServerStarting, port=53 12:03:31.706 [main ] INF com.mageddo.http.WebServer l=134 m=start status=startingWebServer, port=5380 12:03:36.733 [Thread-3 ] INF c.m.d.dnsconfigurator.DnsConfigurators l=113 m=getInstance0 usingDnsConfigurator=DnsConfiguratorLinux 12:03:36.733 [Thread-3 ] INF c.m.d.dnsconfigurator.linux.DnsConfiguratorLinux l=122 m=init status=using, configFile=ResolvFile(path=/host/etc/systemd/resolved.conf, type=SYSTEMD_RESOLVED) 12:03:36.738 [Thread-3 ] WAR c.m.d.dnsconfigurator.linux.DnsConfiguratorLinux l=145 m=tryRestartResolved status=can't restart resolved service, please run: 'service systemd-resolved restart' to apply DPS as default DNS. Not possible to restart resolved service: 1 : systemd-resolved: unrecognized service ```
kerem commented 2026-02-26 04:34:20 +03:00
Author
Owner
Copy link

@mageddo commented on GitHub (Sep 30, 2024):

Hey @ratcashdev , DPS won´t be able to configure itself as the default DNS when running inside a docker container when the host is using system-resolved.

Yep, you will do need to restart systemd-resolved using service or systemctl command, see more details about the limitation.

If you are using DPS as your primary DNS solver I would recommend follow theses steps to configure it as a service and don't have to reconfigure systemd-resolved at every restart.

In alternative you can bypass systemd-resolved and use resolv.conf without the need to restart any service by following these instructions:

services:
  dns-proxy:
    image: defreitas/dns-proxy-server
    hostname: dns
    volumes:
      - type: bind
        source: /var/run/docker.sock
        target: /var/run/docker.sock
      - type: bind
        source: /etc
        target: /host/etc
   environment: 
     - MG_RESOLVCONF=/host/etc/resolv.conf
    ports:
      - "5380:5380"
<!-- gh-comment-id:2383405264 --> @mageddo commented on GitHub (Sep 30, 2024): Hey @ratcashdev , DPS won´t be able to configure itself as the default DNS when running inside a docker container when the host is using system-resolved. Yep, you will do need to restart systemd-resolved using service or systemctl command, [see more details about the limitation][1]. If you are using DPS as your primary DNS solver I would recommend follow [theses steps][2] to configure it as a service and don't have to reconfigure systemd-resolved at every restart. In alternative you can bypass systemd-resolved and use resolv.conf without the need to restart any service by following these instructions: ```yaml services: dns-proxy: image: defreitas/dns-proxy-server hostname: dns volumes: - type: bind source: /var/run/docker.sock target: /var/run/docker.sock - type: bind source: /etc target: /host/etc environment: - MG_RESOLVCONF=/host/etc/resolv.conf ports: - "5380:5380" ``` [1]: https://mageddo.github.io/dns-proxy-server/latest/en/2-features/auto-configuration-as-default-dns/#docker-limitations [2]: https://mageddo.github.io/dns-proxy-server/latest/en/1-getting-started/running-it/linux/#running-as-docker-service
kerem commented 2026-02-26 04:34:20 +03:00
Author
Owner
Copy link

@ratcashdev commented on GitHub (Sep 30, 2024):

HI @mageddo thanks for the quick replay and solution.

DPS won´t be able to configure itself as the default DNS when running inside a docker container when the host is using system-resolved.

can you plz elaborate what is the fundamental issue here?

<!-- gh-comment-id:2383422831 --> @ratcashdev commented on GitHub (Sep 30, 2024): HI @mageddo thanks for the quick replay and solution. > DPS won´t be able to configure itself as the default DNS when running inside a docker container when the host is using system-resolved. can you plz elaborate what is the fundamental issue here?
kerem commented 2026-02-26 04:34:20 +03:00
Author
Owner
Copy link

@mageddo commented on GitHub (Sep 30, 2024):

Basically systemd-resolved need to be restarted and it's a host program, a host program can't be executed from the docker container as expected by the isolation principle, DPS is running inside a docker container so it can´t restart the host system-resolved at the host.

<!-- gh-comment-id:2383508043 --> @mageddo commented on GitHub (Sep 30, 2024): Basically systemd-resolved need to be restarted and it's a host program, a host program can't be executed from the docker container as expected by the isolation principle, DPS is running inside a docker container so it can´t restart the host system-resolved at the host.
kerem commented 2026-02-26 04:34:20 +03:00
Author
Owner
Copy link

@ratcashdev commented on GitHub (Oct 1, 2024):

@mageddo I have tried your suggested setup above. Unfortunately, it seems it still does not work.
here are the logs:

dns-proxy-1  | 06:41:24.864 [main           ] DEB c.m.d.config.dataprovider.ConfigPathBuilder       l=37   m=build                           status=configPathBuilt, path=/app/conf/config.json
dns-proxy-1  | 06:41:24.874 [main           ] INF c.m.dnsproxyserver.config.dataprovider.JsonConfigsl=69   m=createDefaultConfigOnPath       status=createdDefaultConfigFile, path=/app/conf/config.json
dns-proxy-1  | 06:41:24.874 [main           ] DEB c.m.d.config.dataprovider.ConfigDAOJson           l=32   m=find                            configPath=/app/conf/config.json
dns-proxy-1  | 06:41:24.890 [main           ] INF c.m.d.s.d.a.DpsDockerEnvironmentSetupService      l=32   m=setup                           status=binding-docker-events, connectedToDocker=true
dns-proxy-1  | 06:41:24.890 [main           ] INF c.m.d.s.d.a.DpsDockerEnvironmentSetupService      l=44   m=setupNetwork                    status=dpsNetwork, active=false
dns-proxy-1  | 06:41:24.890 [main           ] INF c.m.d.s.docker.application.DpsContainerService    l=116  m=tRunningContainersToDpsNetwork  status=autoConnectDpsNetworkDisabled, dpsNetwork=false, dpsNetworkAutoConnect=false
dns-proxy-1  | 06:41:24.890 [main           ] INF c.m.d.solver.docker.entrypoint.EventListener      l=32   m=onStart                         status=containerAutoConnectToDpsNetworkDisabled
dns-proxy-1  | 06:41:24.890 [main           ] INF com.mageddo.dnsserver.UDPServerPool               l=31   m=start                           Starting UDP server, addresses=/0.0.0.0:53
dns-proxy-1  | 06:41:24.890 [main           ] INF c.mageddo.dnsproxyserver.server.dns.ServerStarter l=30   m=start                           status=startingDnsServer, protocol=UDP_TCP, port=53
dns-proxy-1  | 06:41:24.892 [virtual-44     ] INF com.mageddo.dnsserver.TCPServer                   l=56   m=start0                          status=tcpServerStarting, port=53
dns-proxy-1  | 06:41:24.897 [main           ] INF com.mageddo.http.WebServer                        l=134  m=start                           status=startingWebServer, port=5380
dns-proxy-1  | 06:41:29.911 [Thread-2       ] INF c.m.d.dnsconfigurator.DnsConfigurators            l=113  m=getInstance0                    usingDnsConfigurator=DnsConfiguratorLinux
dns-proxy-1  | 06:41:29.911 [Thread-2       ] INF c.m.d.dnsconfigurator.linux.DnsConfiguratorLinux  l=91   m=lambda$findBestConfFile$0       status=noValidConfFile, file=/host/etc/resolv.conf
dns-proxy-1  | 06:41:29.911 [Thread-2       ] INF c.m.d.dnsconfigurator.linux.DnsConfiguratorLinux  l=122  m=init                            status=using, configFile=null

/etc/resolv.conf still stays the same, containing nameserver 127.0.0.53

<!-- gh-comment-id:2384926382 --> @ratcashdev commented on GitHub (Oct 1, 2024): @mageddo I have tried your suggested setup above. Unfortunately, it seems it still does not work. here are the logs: ``` dns-proxy-1 | 06:41:24.864 [main ] DEB c.m.d.config.dataprovider.ConfigPathBuilder l=37 m=build status=configPathBuilt, path=/app/conf/config.json dns-proxy-1 | 06:41:24.874 [main ] INF c.m.dnsproxyserver.config.dataprovider.JsonConfigsl=69 m=createDefaultConfigOnPath status=createdDefaultConfigFile, path=/app/conf/config.json dns-proxy-1 | 06:41:24.874 [main ] DEB c.m.d.config.dataprovider.ConfigDAOJson l=32 m=find configPath=/app/conf/config.json dns-proxy-1 | 06:41:24.890 [main ] INF c.m.d.s.d.a.DpsDockerEnvironmentSetupService l=32 m=setup status=binding-docker-events, connectedToDocker=true dns-proxy-1 | 06:41:24.890 [main ] INF c.m.d.s.d.a.DpsDockerEnvironmentSetupService l=44 m=setupNetwork status=dpsNetwork, active=false dns-proxy-1 | 06:41:24.890 [main ] INF c.m.d.s.docker.application.DpsContainerService l=116 m=tRunningContainersToDpsNetwork status=autoConnectDpsNetworkDisabled, dpsNetwork=false, dpsNetworkAutoConnect=false dns-proxy-1 | 06:41:24.890 [main ] INF c.m.d.solver.docker.entrypoint.EventListener l=32 m=onStart status=containerAutoConnectToDpsNetworkDisabled dns-proxy-1 | 06:41:24.890 [main ] INF com.mageddo.dnsserver.UDPServerPool l=31 m=start Starting UDP server, addresses=/0.0.0.0:53 dns-proxy-1 | 06:41:24.890 [main ] INF c.mageddo.dnsproxyserver.server.dns.ServerStarter l=30 m=start status=startingDnsServer, protocol=UDP_TCP, port=53 dns-proxy-1 | 06:41:24.892 [virtual-44 ] INF com.mageddo.dnsserver.TCPServer l=56 m=start0 status=tcpServerStarting, port=53 dns-proxy-1 | 06:41:24.897 [main ] INF com.mageddo.http.WebServer l=134 m=start status=startingWebServer, port=5380 dns-proxy-1 | 06:41:29.911 [Thread-2 ] INF c.m.d.dnsconfigurator.DnsConfigurators l=113 m=getInstance0 usingDnsConfigurator=DnsConfiguratorLinux dns-proxy-1 | 06:41:29.911 [Thread-2 ] INF c.m.d.dnsconfigurator.linux.DnsConfiguratorLinux l=91 m=lambda$findBestConfFile$0 status=noValidConfFile, file=/host/etc/resolv.conf dns-proxy-1 | 06:41:29.911 [Thread-2 ] INF c.m.d.dnsconfigurator.linux.DnsConfiguratorLinux l=122 m=init status=using, configFile=null ``` `/etc/resolv.conf` still stays the same, containing `nameserver 127.0.0.53`
kerem commented 2026-02-26 04:34:20 +03:00
Author
Owner
Copy link

@mageddo commented on GitHub (Oct 1, 2024):

I will do a check, looks like DPS hasn't permission to edit resolv.conf

<!-- gh-comment-id:2386296919 --> @mageddo commented on GitHub (Oct 1, 2024): I will do a check, looks like DPS hasn't permission to edit `resolv.conf`
kerem commented 2026-02-26 04:34:20 +03:00
Author
Owner
Copy link

@ratcashdev commented on GitHub (Oct 1, 2024):

yeah, pretty much:

-rw-r--r-- 1 systemd-resolve systemd-resolve 920 sep 30 16:23 /run/systemd/resolve/stub-resolv.conf
<!-- gh-comment-id:2386555159 --> @ratcashdev commented on GitHub (Oct 1, 2024): yeah, pretty much: ``` -rw-r--r-- 1 systemd-resolve systemd-resolve 920 sep 30 16:23 /run/systemd/resolve/stub-resolv.conf ```
kerem commented 2026-02-26 04:34:20 +03:00
Author
Owner
Copy link

@mageddo commented on GitHub (Oct 7, 2024):

@ratcashdev

Got it.

/host/etc/resolv.conf is a symlink

# ls -lha /host/etc/resolv*
lrwxrwxrwx 1 root root   39 Sep 15  2022 /host/etc/resolv.conf -> ../run/systemd/resolve/stub-resolv.conf

So you need to run like below:

services:
  dns-proxy:
    image: defreitas/dns-proxy-server
    hostname: dns
    volumes:
      - /run/systemd/resolve/:/host/run/
    environment:
      MG_RESOLVCONF: /host/run/stub-resolv.conf
    ports:
      - "5380:5380"


dns-proxy-1  | 13:00:31.189 [Thread-3       ] INF c.m.d.dnsconfigurator.linux.DnsConfiguratorLinux  l=122  m=init                            status=using, configFile=ResolvFile(path=/host/run/stub-resolv.conf, type=RESOLVCONF)

Improving the logs to make the failing condition explicit at #585 .

<!-- gh-comment-id:2396867271 --> @mageddo commented on GitHub (Oct 7, 2024): @ratcashdev Got it. `/host/etc/resolv.conf` is a symlink ```bash # ls -lha /host/etc/resolv* lrwxrwxrwx 1 root root 39 Sep 15 2022 /host/etc/resolv.conf -> ../run/systemd/resolve/stub-resolv.conf ``` So you need to run like below: ```yaml services: dns-proxy: image: defreitas/dns-proxy-server hostname: dns volumes: - /run/systemd/resolve/:/host/run/ environment: MG_RESOLVCONF: /host/run/stub-resolv.conf ports: - "5380:5380" ``` ``` dns-proxy-1 | 13:00:31.189 [Thread-3 ] INF c.m.d.dnsconfigurator.linux.DnsConfiguratorLinux l=122 m=init status=using, configFile=ResolvFile(path=/host/run/stub-resolv.conf, type=RESOLVCONF) ``` Improving the logs to make the failing condition explicit at #585 .
kerem commented 2026-02-26 04:34:20 +03:00
Author
Owner
Copy link

@github-actions[bot] commented on GitHub (Oct 23, 2024):

This issue is stale because it has been waiting-feedback for 15 days with no activity.

<!-- gh-comment-id:2431158401 --> @github-actions[bot] commented on GitHub (Oct 23, 2024): This issue is stale because it has been waiting-feedback for 15 days with no activity.
kerem commented 2026-02-26 04:34:20 +03:00
Author
Owner
Copy link

@github-actions[bot] commented on GitHub (Oct 31, 2024):

This issue was closed because it has been inactive for 7 days since being marked as stale, you can reopen it at any time.

<!-- gh-comment-id:2449219059 --> @github-actions[bot] commented on GitHub (Oct 31, 2024): This issue was closed because it has been inactive for 7 days since being marked as stale, you can reopen it at any time.
kerem commented 2026-02-26 04:34:20 +03:00
Author
Owner
Copy link

@ratcashdev commented on GitHub (Oct 31, 2024):

Tested this today. Unfortunately, it still does not work.

Logs look good, but a simple ping to a hostname registered in the compose file fails.

logs:

dns-proxy-1  | 09:20:45.529 [main           ] DEB c.m.d.config.dataprovider.ConfigPathBuilder       l=37   m=build                           status=configPathBuilt, path=/app/conf/config.json
dns-proxy-1  | 09:20:45.536 [main           ] INF c.m.dnsproxyserver.config.dataprovider.JsonConfigsl=69   m=createDefaultConfigOnPath       status=createdDefaultConfigFile, path=/app/conf/config.json
dns-proxy-1  | 09:20:45.537 [main           ] DEB c.m.d.config.dataprovider.ConfigDAOJson           l=32   m=find                            configPath=/app/conf/config.json
dns-proxy-1  | 09:20:45.553 [main           ] INF c.m.d.s.d.a.DpsDockerEnvironmentSetupService      l=32   m=setup                           status=binding-docker-events, connectedToDocker=true
dns-proxy-1  | 09:20:45.553 [main           ] INF c.m.d.s.d.a.DpsDockerEnvironmentSetupService      l=44   m=setupNetwork                    status=dpsNetwork, active=false
dns-proxy-1  | 09:20:45.553 [main           ] INF c.m.d.s.docker.application.DpsContainerService    l=116  m=tRunningContainersToDpsNetwork  status=autoConnectDpsNetworkDisabled, dpsNetwork=false, dpsNetworkAutoConnect=false
dns-proxy-1  | 09:20:45.553 [main           ] INF c.m.d.solver.docker.entrypoint.EventListener      l=32   m=onStart                         status=containerAutoConnectToDpsNetworkDisabled
dns-proxy-1  | 09:20:45.554 [main           ] INF com.mageddo.dnsserver.UDPServerPool               l=31   m=start                           Starting UDP server, addresses=/0.0.0.0:53
dns-proxy-1  | 09:20:45.554 [main           ] INF c.mageddo.dnsproxyserver.server.dns.ServerStarter l=30   m=start                           status=startingDnsServer, protocol=UDP_TCP, port=53
dns-proxy-1  | 09:20:45.556 [virtual-44     ] INF com.mageddo.dnsserver.TCPServer                   l=56   m=start0                          status=tcpServerStarting, port=53
dns-proxy-1  | 09:20:45.562 [main           ] INF com.mageddo.http.WebServer                        l=134  m=start                           status=startingWebServer, port=5380
dns-proxy-1  | 09:20:50.603 [Thread-3       ] INF c.m.d.dnsconfigurator.DnsConfigurators            l=113  m=getInstance0                    usingDnsConfigurator=DnsConfiguratorLinux
dns-proxy-1  | 09:20:50.604 [Thread-3       ] INF c.m.d.dnsconfigurator.linux.DnsConfiguratorLinux  l=122  m=init                            status=using, configFile=ResolvFile(path=/host/run/stub-resolv.conf, type=RESOLVCONF)

/etc/resolv.conf (linked to /run/systemd/resolve/stub-resolv.conf) now looks like this:

# nameserver 127.0.0.53 # dps-comment
options edns0 trust-ad
search .
nameserver 172.18.0.2 # dps-entry
<!-- gh-comment-id:2449411198 --> @ratcashdev commented on GitHub (Oct 31, 2024): Tested this today. Unfortunately, it still does not work. Logs look good, but a simple ping to a hostname registered in the compose file fails. logs: ``` dns-proxy-1 | 09:20:45.529 [main ] DEB c.m.d.config.dataprovider.ConfigPathBuilder l=37 m=build status=configPathBuilt, path=/app/conf/config.json dns-proxy-1 | 09:20:45.536 [main ] INF c.m.dnsproxyserver.config.dataprovider.JsonConfigsl=69 m=createDefaultConfigOnPath status=createdDefaultConfigFile, path=/app/conf/config.json dns-proxy-1 | 09:20:45.537 [main ] DEB c.m.d.config.dataprovider.ConfigDAOJson l=32 m=find configPath=/app/conf/config.json dns-proxy-1 | 09:20:45.553 [main ] INF c.m.d.s.d.a.DpsDockerEnvironmentSetupService l=32 m=setup status=binding-docker-events, connectedToDocker=true dns-proxy-1 | 09:20:45.553 [main ] INF c.m.d.s.d.a.DpsDockerEnvironmentSetupService l=44 m=setupNetwork status=dpsNetwork, active=false dns-proxy-1 | 09:20:45.553 [main ] INF c.m.d.s.docker.application.DpsContainerService l=116 m=tRunningContainersToDpsNetwork status=autoConnectDpsNetworkDisabled, dpsNetwork=false, dpsNetworkAutoConnect=false dns-proxy-1 | 09:20:45.553 [main ] INF c.m.d.solver.docker.entrypoint.EventListener l=32 m=onStart status=containerAutoConnectToDpsNetworkDisabled dns-proxy-1 | 09:20:45.554 [main ] INF com.mageddo.dnsserver.UDPServerPool l=31 m=start Starting UDP server, addresses=/0.0.0.0:53 dns-proxy-1 | 09:20:45.554 [main ] INF c.mageddo.dnsproxyserver.server.dns.ServerStarter l=30 m=start status=startingDnsServer, protocol=UDP_TCP, port=53 dns-proxy-1 | 09:20:45.556 [virtual-44 ] INF com.mageddo.dnsserver.TCPServer l=56 m=start0 status=tcpServerStarting, port=53 dns-proxy-1 | 09:20:45.562 [main ] INF com.mageddo.http.WebServer l=134 m=start status=startingWebServer, port=5380 dns-proxy-1 | 09:20:50.603 [Thread-3 ] INF c.m.d.dnsconfigurator.DnsConfigurators l=113 m=getInstance0 usingDnsConfigurator=DnsConfiguratorLinux dns-proxy-1 | 09:20:50.604 [Thread-3 ] INF c.m.d.dnsconfigurator.linux.DnsConfiguratorLinux l=122 m=init status=using, configFile=ResolvFile(path=/host/run/stub-resolv.conf, type=RESOLVCONF) ``` /etc/resolv.conf (linked to /run/systemd/resolve/stub-resolv.conf) now looks like this: ``` # nameserver 127.0.0.53 # dps-comment options edns0 trust-ad search . nameserver 172.18.0.2 # dps-entry ```
kerem commented 2026-02-26 04:34:20 +03:00
Author
Owner
Copy link

@mageddo commented on GitHub (Oct 31, 2024):

@ratcashdev can you confirm that DPS is being used as the default DNS? can you see query entries at DPS logs?

If your /etc/resolv.conf keeps with nameserver 172.18.0.2 # dps-entry then it's supposed to work.

You can ping dps-sample.dev or host.docker to check if DPS is working.

<!-- gh-comment-id:2450152848 --> @mageddo commented on GitHub (Oct 31, 2024): @ratcashdev can you confirm that DPS is being used as the default DNS? can you see query entries at DPS logs? If your /etc/resolv.conf keeps with `nameserver 172.18.0.2 # dps-entry` then it's supposed to work. You can ping `dps-sample.dev` or `host.docker` to check if DPS is working.
kerem commented 2026-02-26 04:34:20 +03:00
Author
Owner
Copy link

@ratcashdev commented on GitHub (Oct 31, 2024):

@mageddo unfortunately none of the pings work and I don't see any name queries in the DPS logs.

<!-- gh-comment-id:2450326235 --> @ratcashdev commented on GitHub (Oct 31, 2024): @mageddo unfortunately none of the pings work and I don't see any name queries in the DPS logs.
kerem commented 2026-02-26 04:34:20 +03:00
Author
Owner
Copy link

@mageddo commented on GitHub (Oct 31, 2024):

Looks like systemd-resolved is acting and ignoring resolv.conf. If you really want to run DPS inside docker container you can set an static IP for DPS container and configure it on systemd-resolved as following (you will need to use DPS 3.30.5-snapshot):

services:
  dns-proxy:
    image: defreitas/dns-proxy-server:3.30.5-snapshot
    hostname: dns
    volumes:
      - type: bind
        source: /var/run/docker.sock
        target: /var/run/docker.sock
    networks:
      my_network:
        ipv4_address: 171.18.0.10  
    environment:
      - MG_LOG_LEVEL=DEBUG

networks:
  my_network:
    driver: bridge
    ipam:
      config:
        - subnet: 171.18.0.0/16

sudo nano /etc/systemd/resolved.conf

Locate the DNS= line in the [Resolve] section and add the container's static IP:

[Resolve]
DNS=171.18.0.10 
FallbackDNS=

Restart the systemd-resolved service to apply the changes: DPS will be used when available

sudo systemctl restart systemd-resolved
<!-- gh-comment-id:2450551869 --> @mageddo commented on GitHub (Oct 31, 2024): Looks like systemd-resolved is acting and ignoring resolv.conf. If you really want to run DPS inside docker container you can set an static IP for DPS container and configure it on systemd-resolved as following (you will need to use DPS 3.30.5-snapshot): ```yaml services: dns-proxy: image: defreitas/dns-proxy-server:3.30.5-snapshot hostname: dns volumes: - type: bind source: /var/run/docker.sock target: /var/run/docker.sock networks: my_network: ipv4_address: 171.18.0.10 environment: - MG_LOG_LEVEL=DEBUG networks: my_network: driver: bridge ipam: config: - subnet: 171.18.0.0/16 ``` ``` sudo nano /etc/systemd/resolved.conf ``` Locate the DNS= line in the [Resolve] section and add the container's static IP: ```ini [Resolve] DNS=171.18.0.10 FallbackDNS= ``` Restart the systemd-resolved service to apply the changes: DPS will be used when available ```bash sudo systemctl restart systemd-resolved ```
kerem commented 2026-02-26 04:34:20 +03:00
Author
Owner
Copy link

@ratcashdev commented on GitHub (Nov 11, 2024):

Thanks for the suggestion. My primary use case was to start dns-proxy from inside docker-compose to allow seamless communication between the host and other containers using host names during integration testing. The requirement to restart resolved makes this a non-practical approach (to the extent of being practically unusable) for my use case.
Thanks for your efforts, either way!

<!-- gh-comment-id:2467951165 --> @ratcashdev commented on GitHub (Nov 11, 2024): Thanks for the suggestion. My primary use case was to start dns-proxy from inside docker-compose to allow seamless communication between the host and other containers using host names during integration testing. The requirement to restart resolved makes this a non-practical approach (to the extent of being practically unusable) for my use case. Thanks for your efforts, either way!
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
master
gh-pages
develop
feat/138_2
feat/629
feat/594
5.9.0
5.9.0-snapshot
5.8.4
5.8.4-snapshot
5.8.3-snapshot
5.8.2-snapshot
5.8.1-snapshot
5.8.0-snapshot
5.7.0-snapshot
5.6.2-snapshot
5.6.1-snapshot
5.6.0-snapshot
5.5.1-snapshot
5.5.0-snapshot
5.4.0-snapshot
5.3.0-snapshot
5.2.0-snapshot
5.1.3-snapshot
5.1.2-snapshot
5.1.0-snapshot
5.0.5-snapshot
5.0.3-snapshot
5.0.2-snapshot
5.0.1-snapshot
5.0.0-snapshot
4.3.0-snapshot
4.2.0-snapshot
4.0.0
4.0.0-snapshot
3.32.7
3.32.7-snapshot
3.32.6
3.32.6-snapshot
3.32.5-snapshot
3.32.4
3.32.4-snapshot
3.32.3
3.32.3-snapshot
3.32.2-snapshot
3.32.1-snapshot
3.32.0-snapshot
3.31.1-snapshot
3.31.0-snapshot
3.30.5-snapshot
3.30.4
3.30.4-snapshot
3.30.3-snapshot
3.30.2-snapshot
3.30.1
3.30.1-snapshot
3.30.0-snapshot
3.29.0-snapshot
3.27.0
3.27.0-snapshot
3.26.0-snapshot
3.25.14
3.25.14-snapshot
3.25.13-snapshot
3.25.12-snapshot
3.25.11
3.25.11-snapshot
3.25.10
3.25.10-snapshot
3.25.9-snapshot
3.25.8-snapshot
3.25.7-snapshot
3.25.6-snapshot
3.25.4-snapshot
3.25.3-snapshot
3.25.2-snapshot
3.25.1-snapshot
3.25.0-snapshot
3.24.2
3.24.2-snapshot
3.24.1
3.24.1-snapshot
3.24.0-snapshot
3.23.0-snapshot
3.22.2-snapshot
3.22.3-snapshot
3.22.1-snapshot
3.21.3-snapshot
3.22.0-snapshot
3.21.2-snapshot
3.21.1-snapshot
3.20.0-snapshot
3.21.0-snapshot
3.19.7-snapshot
3.19.6-snapshot
3.19.5-snapshot
3.19.4-snapshot
3.19.3-snapshot
3.19.2-snapshot
3.19.1
3.19.1-snapshot
3.19.0
3.18.5-snapshot
3.18.4-snapshot
3.18.3-snapshot
3.18.2
3.18.2-snapshot
3.18.1-snapshot
3.18.0-snapshot
3.17.3-snapshot
3.17.2-snapshot
3.17.1-snapshot
3.17.0-snapshot
3.16.3-snapshot
3.16.2-snapshot
3.16.1-snapshot
3.16.0-snapshot
3.15.13-snapshot
3.15.12-snapshot
3.15.11-snapshot
3.15.10-snapshot
3.15.9-snapshot
3.15.8-snapshot
3.15.7-snapshot
3.15.6-snapshot
3.15.5-snapshot
3.15.4-snapshot
3.15.3-snapshot
3.15.2-snapshot
3.15.1-snapshot
3.15.0-snapshot
3.14.5
3.14.4
3.14.3
3.14.3-snapshot
3.14.2-snapshot
3.14.1-snapshot
3.14.0-snapshot
3.13.1
3.13.1-snapshot
3.13.0-snapshot
3.12.1
3.12.0
3.11.0
3.10.2-snapshot
3.10.3-snapshot
3.10.4-snapshot
3.10.5-snapshot
3.10.1-snapshot
3.9.2
3.9.1
3.9.0
3.8.1-last-version-with-quarkus
3.8.1
3.8.0
3.7.0
3.6.0
3.5.3
3.5.2
3.5.0
3.4.0-beta
3.3.0-beta
3.2.5-beta
3.2.4-beta
3.2.3-beta
3.2.2-beta
3.2.1-beta
3.2.0-beta
3.1.7-beta
3.1.6-beta
3.1.5-beta
3.1.4-beta
3.1.3-beta
3.1.2-beta
b-jre-8
3.1.1-beta
3.1.0-beta
3.0.4-beta
3.0.3-beta
3.0.2-beta
3.0.1-beta
v2-golang
2.19.5
2.19.4
2.19.3
2.19.2
2.19.1
2.19.0
2.18.7
2.18.6
2.18.5
2.18.4
2.18.3
2.18.2
2.18.1
2.18.0
2.17.4
2.17.3
2.17.2
2.17.1
2.17.0
2.16.0
2.15.0
2.14.6
2.14.5
2.14.4
2.14.2
2.14.1
2.14.0
2.13.2
2.13.1
2.13.0
2.12.0
2.11.0
2.10.4
2.10.3
2.10.2
2.10.1
2.10.0
2.9.1
2.9.0
2.8.0
2.7.0
2.6.1
2.6.0
2.5.4
2.5.3
2.5.2
2.5.1
2.5.0
2.4.1
2.4.0
2.3.3
2.2.3
2.2.2
2.2.1
2.2.0
2.1.8
2.1.7
2.1.6
2.1.5
2.1.2
2.1.1
2.1.0
2.0.21
2.0.20
2.0.19
2.0.18
2.0.17
2.0.16
2.0.9
2.0.5
2.0.4
v1-nodejs
1.8.1
1.8.0
1.7.7
1.7.6
1.7.5
1.7.4
1.7.3
1.7.2
1.7.1
1.7.0
1.6.9
1.6.8
1.6.7
1.6.6
1.6.5
1.6.4
1.6.3
1.6.2
1.6.1
1.6.0
1.5.0
1.4.0
1.3.5
1.3.4
1.3.3
1.3.2
1.3.1
1.3.0
peteris-version
1.1.4-peteris-version
1.2.0
1.1.3
1.1.2
1.1.1
1.1.0
1.0.1
1.0.0
Labels
Clear labels   
bug

   
confirmed

   
discussion

   
duplicate

   
enhancement

   
feature

   
feature-request

   
not-planned

   
pull-request

Mirrored from GitHub Pull Request

  
secondary-feature

   
stale

   
triage

   
waiting-feedback
No labels
bug
confirmed
discussion
duplicate
enhancement
feature
feature-request
not-planned
pull-request
secondary-feature
stale
triage
waiting-feedback
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
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#192
No description provided.