-
Notifications
You must be signed in to change notification settings - Fork 117
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ping -4 works but ping does not work. -> vpnkit dns: extremely slow, with internal unexpected error from dnssd: Timeout (-65568)
#5516
Comments
unexpected error from dnssd: Timeout (-65568)
I experience similar behavior running macOS 11.2.3. My laptop is connected to a VPN using the built-in Cisco VPN client. When running Docker Desktop 3.2.2, the following pull command towards an internal Artifactory instance took 26 seconds to complete for an alpine:latest image that was already up-to-date: $ docker image pull docker.artifactory.tlt.local/alpine:latest
latest: Pulling from alpine
Digest: sha256:dc89ce8401da81f24f7ba3f0ab2914ed9013608bdba0b7e7e5d964817067dc06
Status: Image is up to date for docker.artifactory.tlt.local/alpine:latest
docker.artifactory.tlt.local/alpine:latest The Console log for After upgrading to Docker Desktop 3.3.0, I was entirely unable to pull an image from our local Artifactory Docker repository. $ docker image pull docker.artifactory.tlt.local/alpine:latest
Error response from daemon: Get https://docker.artifactory.tlt.local/v2/: Bad Gateway |
I want to find the relevant source code of this issue and fix them, but could not find it! I often feel that the "open source" is not that open, sometimes you just can not easily find the source code.
|
I have the same problem like @kongslund running macOS 10.14.6 and Docker desktop 3.3.1. |
Same problem with macOS 10.15.7 and Docker Desktop 3.3.1. |
how is it going now? Docker Desktop 3.5.1 still has the issue. |
unexpected error from dnssd: Timeout (-65568)
unexpected error from dnssd: Timeout (-65568)
Facing with the same issue as @jjqq2013 MacOS: Mojave 10.14.6 Docker desktop: 2.5.0 --> working much more faster + ping also working with it. |
this is really an important issue. Docker 3.5.2 still has the same issue. A |
/cc @djs55 |
Did anyone find out any fix for this issue so far ? |
@grendach , if you can change your DNS server's configuration to answer the |
Issues go stale after 90 days of inactivity. Prevent issues from auto-closing with an If this issue is safe to close now please do so. Send feedback to Docker Community Slack channels #docker-for-mac or #docker-for-windows. |
This is not what I experience. On my Mac, Within an Ubuntu 20.04 container, the same command takes 15 seconds to return with |
I've come to realize that This query takes 15 seconds to return.
This query returns immediately when using our internal DNS a.b.c.d directly instead of going through Docker DNS. It means the issue is not with our internal DNS server.
When querying something without
Could it have something to do with the lack of a search domain defined in Is there is way to configure the search domain for the Linux VM? |
Closed issues are locked after 30 days of inactivity. If you have found a problem that seems similar to this, please open a new issue. Send feedback to Docker Community Slack channels #docker-for-mac or #docker-for-windows. |
Expected behavior
DNS queries get response quickly
Actual behavior
DNS queries are very slow
Information
Steps to reproduce the behavior
ping A_FQDN_IN_VPN
ornslookup A_FQDN_IN_VPN
, in any docker container such asping A_FQDN_IN_VPN
always cause 15 seconds to show the IP. Theping -4 A_FQDN_IN_VPN
will immediately show IP. Thenslookup A_FQDN_IN_VPN
cause 5 seconds with following answer:strace
to Built-in DNS server extremely slow for large responses #4430 (comment), turns out thesendto
andrecvfrom
syscall were very slow(5 seconds).Additional information: I've managed to dump to DNS UDP data and time, note the timestamp on right side, the timestamp of first response is 5 seconds later of the request:
BTW, my Macbook has installed "Symantec Endpoint Protection" (an anti-virus software).
Other notable things:
ping an VPN IP from a container always fails, seems like some data are blocked.EDIT: sorry fo confusing, after restart Docker, ping IP works, but ping fqdn still does not work.
all host side dns servers can not be pinged from the container but can be pinged in the host.EDIT: sorry fo confusing, after restart Docker, all host side dns servers can be pinged.
The text was updated successfully, but these errors were encountered: