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 #251] Running dns-proxy-server makes docker image builds fail, with cannot resolve host errors #104

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

Originally created by @SimJoSt on GitHub (Dec 2, 2022).
Original GitHub issue: https://github.com/mageddo/dns-proxy-server/issues/251

What is Happening

  • Building docker images with the need to resolve external dependencies throws "cannot resolve host" errors.

What is expected

Docker image builds are not affected.
Either they resolve normally or through dns-proxy-server

Steps to Reproduce

  1. Have a dns-proxy-server running
  2. Start a Docker image build with the need to resolve external dependencies

Specs:

  • OS: Debian 10 Buster
  • Docker Version: 20.10.21
  • DPS Version: 2.19.0
Originally created by @SimJoSt on GitHub (Dec 2, 2022). Original GitHub issue: https://github.com/mageddo/dns-proxy-server/issues/251 ### What is Happening * Building docker images with the need to resolve external dependencies throws "cannot resolve host" errors. ### What is expected Docker image builds are not affected. Either they resolve normally or through dns-proxy-server ### Steps to Reproduce 1. Have a dns-proxy-server running 2. Start a Docker image build with the need to resolve external dependencies **Specs:** - OS: Debian 10 Buster - Docker Version: 20.10.21 - DPS Version: 2.19.0
kerem closed this issue 2026-02-26 04:34:03 +03:00
kerem commented 2026-02-26 04:34:03 +03:00
Author
Owner
Copy link

@zxzharmlesszxz commented on GitHub (Feb 15, 2023):

UP!

<!-- gh-comment-id:1431340153 --> @zxzharmlesszxz commented on GitHub (Feb 15, 2023): UP!
kerem commented 2026-02-26 04:34:03 +03:00
Author
Owner
Copy link

@mageddo commented on GitHub (Feb 23, 2023):

Hey, I wasn't able to reproduce this behavior, What I noticed is that docker caches the DNS server address, so if you start DPS, restart docker, then restart DPS again and it get a new docker container IP then you can get an issue, because docker cached the previous DPS IP and will try to solve names from an IP that is not DPS server anymore. I think there's no much DPS can do in this case.

Can you please confirm if your usecase is something like that or give more details on the steps to reproduce it?

If your usecase is the mentioned, then you can lead with this by fixing a IP address to the DPS container by using docker run --ip ... .

Thanks in advance.

<!-- gh-comment-id:1441196639 --> @mageddo commented on GitHub (Feb 23, 2023): Hey, I wasn't able to reproduce this behavior, What I noticed is that docker caches the DNS server address, so if you start DPS, restart docker, then restart DPS again and it get a new docker container IP then you can get an issue, because docker cached the previous DPS IP and will try to solve names from an IP that is not DPS server anymore. I think there's no much DPS can do in this case. Can you please confirm if your usecase is something like that or give more details on the steps to reproduce it? If your usecase is the mentioned, then you can lead with this by fixing a IP address to the DPS container by using `docker run --ip ... ` . Thanks in advance.
kerem commented 2026-02-26 04:34:03 +03:00
Author
Owner
Copy link

@mageddo commented on GitHub (Feb 23, 2023):

@zxzharmlesszxz @SimJoSt

<!-- gh-comment-id:1441197045 --> @mageddo commented on GitHub (Feb 23, 2023): @zxzharmlesszxz @SimJoSt
kerem commented 2026-02-26 04:34:03 +03:00
Author
Owner
Copy link

@mageddo commented on GitHub (Feb 23, 2023):

I've noticed that this can be related to this one https://github.com/mageddo/dns-proxy-server/issues/248, if DPS use systemd-resolved instead of the resolv.conf file this issue may disappear

<!-- gh-comment-id:1441234335 --> @mageddo commented on GitHub (Feb 23, 2023): I've noticed that this can be related to this one https://github.com/mageddo/dns-proxy-server/issues/248, if DPS use systemd-resolved instead of the resolv.conf file this issue may disappear
kerem commented 2026-02-26 04:34:03 +03:00
Author
Owner
Copy link

@SimJoSt commented on GitHub (Feb 23, 2023):

We don't restart the containers that much on their own, so I don't think thus would be it. Of course it could be possible.
I'll check that out on the next maintenance.
It will take a few days at least to confirm this is fixes the issue.

<!-- gh-comment-id:1441501538 --> @SimJoSt commented on GitHub (Feb 23, 2023): We don't restart the containers that much on their own, so I don't think thus would be it. Of course it could be possible. I'll check that out on the next maintenance. It will take a few days at least to confirm this is fixes the issue.
kerem commented 2026-02-26 04:34:03 +03:00
Author
Owner
Copy link

@zxzharmlesszxz commented on GitHub (Feb 24, 2023):

It is possible if you run dns-proxy container at the different network than other containers, example:

  • run dns-proxy at dns network
  • run test container at the test network
    What's happened?
    DNS not resolved!
    Example 2:
    When your dns-proxy container is running at different than default network,
    run build container command, what happens:
  • DNS-proxy at the different network
  • build process running at the default network
    Build process doesn't have access to dns-proxy to resolve names
<!-- gh-comment-id:1442793183 --> @zxzharmlesszxz commented on GitHub (Feb 24, 2023): It is possible if you run dns-proxy container at the different network than other containers, example: - run dns-proxy at dns network - run test container at the test network What's happened? DNS not resolved! Example 2: When your dns-proxy container is running at different than default network, run build container command, what happens: - DNS-proxy at the different network - build process running at the default network Build process doesn't have access to dns-proxy to resolve names
kerem commented 2026-02-26 04:34:03 +03:00
Author
Owner
Copy link

@mageddo commented on GitHub (Feb 25, 2023):

Hey @zxzharmlesszxz , it would be easier to understand the scenario with a minimal reproducible example, focusing on your first example, I tried the below but still works

version: '3'
services:
  dps:
    image: defreitas/dns-proxy-server:2.19.0
    volumes:
      - /var/run/docker.sock:/var/run/docker.sock
      - /etc/resolv.conf:/etc/resolv.conf
    hostname: dns.mageddo
    networks:
      dns:
  nginx:
    image: nginx:1.22
    hostname: nginx.app
    networks:
      test:

networks:
  dns:
  test:


curl -I nginx.app
HTTP/1.1 200 OK
Server: nginx/1.22.1
<!-- gh-comment-id:1445113689 --> @mageddo commented on GitHub (Feb 25, 2023): Hey @zxzharmlesszxz , it would be easier to understand the scenario with a minimal reproducible example, focusing on your first example, I tried the below but still works ```yml version: '3' services: dps: image: defreitas/dns-proxy-server:2.19.0 volumes: - /var/run/docker.sock:/var/run/docker.sock - /etc/resolv.conf:/etc/resolv.conf hostname: dns.mageddo networks: dns: nginx: image: nginx:1.22 hostname: nginx.app networks: test: networks: dns: test: ``` ```bash curl -I nginx.app HTTP/1.1 200 OK Server: nginx/1.22.1 ```
kerem commented 2026-02-26 04:34:03 +03:00
Author
Owner
Copy link

@mageddo commented on GitHub (Feb 25, 2023):

Created a section at the docs to add more details about that.

<!-- gh-comment-id:1445120047 --> @mageddo commented on GitHub (Feb 25, 2023): Created a [section][1] at the docs to add more details about that. [1]: http://mageddo.github.io/dns-proxy-server/latest/en/2-features/docker-different-networks-solving/
kerem commented 2026-02-26 04:34:03 +03:00
Author
Owner
Copy link

@zxzharmlesszxz commented on GitHub (Feb 25, 2023):

It's really working, but can you to try build other docker image with models and npm install when this docker-compose containers will working.
At this situation - dns resolves will be failed

<!-- gh-comment-id:1445177883 --> @zxzharmlesszxz commented on GitHub (Feb 25, 2023): It's really working, but can you to try build other docker image with models and npm install when this docker-compose containers will working. At this situation - dns resolves will be failed
kerem commented 2026-02-26 04:34:03 +03:00
Author
Owner
Copy link

@mageddo commented on GitHub (Feb 25, 2023):

@zxzharmlesszxz Maybe your failing use case is related to this thread? #244 If yes we can migrate this discussion to there

<!-- gh-comment-id:1445182207 --> @mageddo commented on GitHub (Feb 25, 2023): @zxzharmlesszxz Maybe your failing use case is related to this thread? #244 If yes we can migrate this discussion to there
kerem commented 2026-02-26 04:34:03 +03:00
Author
Owner
Copy link

@mageddo commented on GitHub (Feb 28, 2023):

The issue #244 was considered fixed, can you test version 3.5.0 and check if your issue persists? If not we can close this one

<!-- gh-comment-id:1447510112 --> @mageddo commented on GitHub (Feb 28, 2023): The issue #244 was considered fixed, can you test version 3.5.0 and check if your issue persists? If not we can close this one
kerem commented 2026-02-26 04:34:03 +03:00
Author
Owner
Copy link

@mageddo commented on GitHub (Mar 2, 2023):

Please re-open it if have any updates

<!-- gh-comment-id:1452115767 --> @mageddo commented on GitHub (Mar 2, 2023): Please re-open it if have any updates
kerem commented 2026-02-26 04:34:03 +03:00
Author
Owner
Copy link

@SimJoSt commented on GitHub (Jul 27, 2023):

@mageddo thanks for the debugging, fixing, development and engagement 🙏

I finally got around to checking all the comments, resources and new releases.
As recommended, I got the binary (https://github.com/mageddo/dns-proxy-server/releases/tag/3.15.13-snapshot) instead of the Docker version. After shutting down the Docker version, confirming that it removed its entries from /etc/resolve.conf, I started it with commands mentioned here: https://mageddo.github.io/dns-proxy-server/3.8/en/1-getting-started/running-it/linux/
I could verify it used the /etc/systemd/resolved.conf file and changed the necessary entries. However, I could not resolve the docker hostnames like nextcloud.docker anymore. Switching back to the preexisting, not-updated Docker version, resolved the issue.

I also tried to install it as a Linux service following the instructions: https://github.com/mageddo/dns-proxy-server/blob/master/docs/content/2-features/installing-as-service/_index.en.md?plain=1#L23
Checking the --help, I also tried -service=normal instead of -service=docker from the docs. None of the registered a service.

Is there anything obvious I might have missed, switching from Docker to binary?
This problem can be moved to a new issue, I just wanted to document the results here, as I have not been able to get it running to test, if the original issue has been resolved.

<!-- gh-comment-id:1653336050 --> @SimJoSt commented on GitHub (Jul 27, 2023): @mageddo thanks for the debugging, fixing, development and engagement 🙏 I finally got around to checking all the comments, resources and new releases. As recommended, I got the binary (https://github.com/mageddo/dns-proxy-server/releases/tag/3.15.13-snapshot) instead of the Docker version. After shutting down the Docker version, confirming that it removed its entries from `/etc/resolve.conf`, I started it with commands mentioned here: https://mageddo.github.io/dns-proxy-server/3.8/en/1-getting-started/running-it/linux/ I could verify it used the `/etc/systemd/resolved.conf` file and changed the necessary entries. However, I could not resolve the docker hostnames like `nextcloud.docker` anymore. Switching back to the preexisting, not-updated Docker version, resolved the issue. I also tried to install it as a Linux service following the instructions: https://github.com/mageddo/dns-proxy-server/blob/master/docs/content/2-features/installing-as-service/_index.en.md?plain=1#L23 Checking the `--help`, I also tried `-service=normal` instead of `-service=docker` from the docs. None of the registered a service. Is there anything obvious I might have missed, switching from Docker to binary? This problem can be moved to a new issue, I just wanted to document the results here, as I have not been able to get it running to test, if the original issue has been resolved.
kerem commented 2026-02-26 04:34:03 +03:00
Author
Owner
Copy link

@mageddo commented on GitHub (Jul 27, 2023):

So you are getting issues with to solve docker containers when running the new version, right? Yep, I agree, please open a new issue describing the reproducing steps

<!-- gh-comment-id:1653813515 --> @mageddo commented on GitHub (Jul 27, 2023): So you are getting issues with to solve docker containers when running the new version, right? Yep, I agree, please open a new issue describing the reproducing steps
kerem commented 2026-02-26 04:34:03 +03:00
Author
Owner
Copy link

@mageddo commented on GitHub (Jul 27, 2023):

@SimJoSt

<!-- gh-comment-id:1653813821 --> @mageddo commented on GitHub (Jul 27, 2023): @SimJoSt
kerem commented 2026-02-26 04:34:03 +03:00
Author
Owner
Copy link

@SimJoSt commented on GitHub (Jul 29, 2023):

@mageddo I have done so: https://github.com/mageddo/dns-proxy-server/issues/424

<!-- gh-comment-id:1656700001 --> @SimJoSt commented on GitHub (Jul 29, 2023): @mageddo I have done so: https://github.com/mageddo/dns-proxy-server/issues/424
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#104
No description provided.