[GH-ISSUE #63] dns resolve during image build #27

Closed
opened 2026-02-26 04:33:48 +03:00 by kerem · 4 comments
Owner

Originally created by @johnbritto1 on GitHub (Apr 3, 2018).
Original GitHub issue: https://github.com/mageddo/dns-proxy-server/issues/63

dns-proxy-log.txt
Hi,

I am using docker eclipse tooling to connect with the remote docker instance using TLS.
The docker build RUN could not resolve dns for command "apt-get install package".
Here is the error shown by dns-proxy-server

18-04-03 06:42:00.016 DEB id=53, m=handleQuestion status=not-resolved, solver=proxy.DockerDnsSolver, err=hostname not found opqobwuqbukhds
18-04-03 06:42:00.016 DEB id=54, m=handleQuestion status=not-resolved, solver=proxy.DockerDnsSolver, err=hostname not found jqwjuxddshtl

Any workaround. If I stop the dns-proxy-server, docker build could resolve the DNS.

I have attached the complete log.

Thanks.

Originally created by @johnbritto1 on GitHub (Apr 3, 2018). Original GitHub issue: https://github.com/mageddo/dns-proxy-server/issues/63 [dns-proxy-log.txt](https://github.com/mageddo/dns-proxy-server/files/1870499/dns-proxy-log.txt) Hi, I am using docker eclipse tooling to connect with the remote docker instance using TLS. The docker build RUN could not resolve dns for command "apt-get install package". Here is the error shown by dns-proxy-server 18-04-03 06:42:00.016 DEB id=53, m=handleQuestion status=not-resolved, solver=proxy.DockerDnsSolver, err=hostname not found opqobwuqbukhds 18-04-03 06:42:00.016 DEB id=54, m=handleQuestion status=not-resolved, solver=proxy.DockerDnsSolver, err=hostname not found jqwjuxddshtl Any workaround. If I stop the dns-proxy-server, docker build could resolve the DNS. I have attached the complete log. Thanks.
kerem closed this issue 2026-02-26 04:33:48 +03:00
Author
Owner

@mageddo commented on GitHub (Apr 28, 2018):

@johnbritto1 Sorry for the too late answer

  1. Which package are you trying to install?
  2. Other command like apt-get update works great?
  3. Are you using DPS at your local machine or at the remote server?

opqobwuqbukhds sounds like a local hostname, I don't think it's related to apt-get. I saw the only one debian server question was successfully answered

18-04-02 15:34:21.039 DEB id=19, m=handleQuestion status=resolved, solver=*proxy.remoteDnsSolver, alength=5, answer=deb.debian.org.	3599	IN	CNAME	static.debian.org.

You could try add a custom DNS server (you can get some taking a look at /etc/resolv.conf) at config file /opt/dns-proxy-server/conf/config.json

{
    "remoteDnsServers": [[0,0,0,0]]
}

Regards

<!-- gh-comment-id:385195197 --> @mageddo commented on GitHub (Apr 28, 2018): @johnbritto1 Sorry for the too late answer 1. Which package are you trying to install? 2. Other command like `apt-get update` works great? 3. Are you using DPS at your local machine or at the remote server? **opqobwuqbukhds** sounds like a local hostname, I don't think it's related to apt-get. I saw the only one debian server question was successfully answered ``` 18-04-02 15:34:21.039 DEB id=19, m=handleQuestion status=resolved, solver=*proxy.remoteDnsSolver, alength=5, answer=deb.debian.org. 3599 IN CNAME static.debian.org. ``` You could try add a custom DNS server (you can get some taking a look at `/etc/resolv.conf`) at config file `/opt/dns-proxy-server/conf/config.json` ```javascript { "remoteDnsServers": [[0,0,0,0]] } Regards
Author
Owner

@johnbritto1 commented on GitHub (Apr 30, 2018):

Hello Mageddo,
Thanks for reply.

To answer you questions.

  1. The build script could not pass after running apt-get update.
  2. I use DPS on remote server.

After adding the dns-server entry in /etc/docker/daemon.json file..

"dns": ["8.8.8.8", "8.8.4.4"],

the issue resolved.

Thanks,
John

<!-- gh-comment-id:385319270 --> @johnbritto1 commented on GitHub (Apr 30, 2018): Hello Mageddo, Thanks for reply. To answer you questions. 1. The build script could not pass after running apt-get update. 2. I use DPS on remote server. After adding the dns-server entry in /etc/docker/daemon.json file.. "dns": ["8.8.8.8", "8.8.4.4"], the issue resolved. Thanks, John
Author
Owner

@mageddo commented on GitHub (Apr 30, 2018):

Thanks for sharing the solution, it would be helpful in the future

<!-- gh-comment-id:385385951 --> @mageddo commented on GitHub (Apr 30, 2018): Thanks for sharing the solution, it would be helpful in the future
Author
Owner

@ilbertt commented on GitHub (Aug 18, 2022):

I'm also had this problem after setting up the dns-proxy-server.
@mageddo do you have any idea of what's causing it?

<!-- gh-comment-id:1219581078 --> @ilbertt commented on GitHub (Aug 18, 2022): I'm also had this problem after setting up the **dns-proxy-server**. @mageddo do you have any idea of what's causing it?
Sign in to join this conversation.
No milestone
No project
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#27
No description provided.