mirror of
https://github.com/mageddo/dns-proxy-server.git
synced 2026-04-25 09:25:56 +03:00
[GH-ISSUE #201] host.docker can't be resolved #82
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#82
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 @c93614 on GitHub (Jun 15, 2020).
Original GitHub issue: https://github.com/mageddo/dns-proxy-server/issues/201
What is Happening
dps can't resolve
host.dockerand error occurs.Steps to Reproduce
host.dockercan't be resolved both in host or in another container.Specs:
@mageddo commented on GitHub (Jul 9, 2020):
It's crashing right here, then it means the resolved gateway IP is not a valid one, try to enable debug logs and find for
status=FindDpsNetworkGatewayIp, ip=orstatus=FindDockerNetworkNetworkGatewayIp, ipat the logs.I will download centos and try to simulate the issue, maybe it's related to centos, or maybe just related with your specific installation.
@mageddo commented on GitHub (Jul 9, 2020):
You can change the log level by changing it's config
@Sajito commented on GitHub (Aug 18, 2020):
Hello @mageddo, I'm having the same issue. Not sure what I should look for, but here's the log output with log level set to "DEBUG".
As OS I'm using Ubuntu 20.04.
Docker version: 19.03.8.
Not sure what additional information you might need.
@ferrine commented on GitHub (Feb 16, 2022):
Same issue here, same logs and same setup
@ferrine commented on GitHub (Feb 16, 2022):
Once it appears I weirdly have resolv.conf misconfigured
@mageddo commented on GitHub (Mar 2, 2023):
Hey @ferrine your evidence is really precious, I worked at more ways to retrieve some valid IP to configure the nameserver and don't get an empty IP as in your cause, can give a try at version 3.5.2?
PSC @Sajito it may help you, if can give it a try...
@mageddo commented on GitHub (Mar 3, 2023):
I'm closing this but feel free to reopen if you need