Comments (13)
rn
commented on August 26, 2024
1
@l8nite we have a PR for hopefully fixing the DNS issue, so it should hopefully show up in the next Beta
from for-win.
rn
commented on August 26, 2024
@l8nite Thanks for your detailed report and analysis. You are correct, we intercept DNS query and currently only forward it to one (the first) DNS server. We are working on fixing this
from for-win.
l8nite
commented on August 26, 2024
@rneugeba rneugeba any ideas on a workaround I can use in the meantime? Is the DNS proxy source around here somewhere? Wondering if I can tweak it for my specific use-case (i.e., pick a different nameserver if the domain being queried isn't my corporate domain).
Edit: I found this, seems to be what I need: https://github.com/ekristen/dns-proxy
Edit 2: I can't get it to play nicely with the docker proxy, but if I run the dns-proxy in a container and then pass --dns=<container-IP-of-dns-proxy> to my other containers, things work as expected.
from for-win.
dgageot
commented on August 26, 2024
@l8nite A new version (Beta25) was released yesterday with fixes to the network/dns stack. Could you please give it a try and tell us if you see an improvement? Thanks a lot!
from for-win.
l8nite
commented on August 26, 2024
@dgageot unfortunately it doesn't appear to have been resolved. It's actually worse now, as when I'm connected to the VPN I can no longer resolve internal OR external names.
from for-win.
dgageot
commented on August 26, 2024
ping @ebriney Coud you please try to debug @l8nite's DNS configuration and understand why we don't pick the right one? Thanks
from for-win.
ebriney
commented on August 26, 2024
@l8nite Can you give me a new diagnostic id?
Because using your user id D90C5FE2-32AC-486E-AB8E-EF1EF4E0036E, there is only the previous bug report info.
Thanks for the help.
from for-win.
l8nite
commented on August 26, 2024
@ebriney I will reproduce and provide a new diagnostic ID tomorrow. I don't have access to my windows machine at the moment.
from for-win.
rn
commented on August 26, 2024
@l8nite is there any update? We are keen to improve the experience for VPN users but if the update helped we would like to close this issue
thanks
from for-win.
dgageot
commented on August 26, 2024
I'm going to close the issue since nobody complained nor responded lately. Feel free to reopen in case the issue is still there of course!
from for-win.
CloningMishap
commented on August 26, 2024
@dgageot Thanks! I just tested it out and it appears to be fixed. I can now ping google.com from inside the container while connected to my Split-VPN through AnyConnect.
from for-win.
l8nite
commented on August 26, 2024
@dgageot This is still failing here on latest beta version. Let me know if it would be better to file a different github issue, because I am experiencing slightly different behavior this time.
Edit: Better formatted bug report.
Not connected to VPN
Let's establish that things are working as expected before we try anything.
First, let's ping google.com from the host machine:
$ ping google.com
Pinging google.com [216.58.194.206] with 32 bytes of data:
And let's try an internal name pf-int-cake1.hq.practicefusion.com from the host machine:
$ ping pf-int-cake1.hq.practicefusion.com
Ping request could not find host pf-int-cake1.hq.practicefusion.com. Please check the name and try again.
We're not on the VPN, so these are the expected results.
Now let's try from within docker containers.
First up, google.com from within a container:
$ docker run --rm -it alpine sh
/ # ping google.com
PING google.com (216.58.194.206): 56 data bytes
So far so good. Here are the logs from this call:
[11:45:18.192][VpnKit ][Debug ] com.docker.slirp.exe: DNS[5857] 192.168.65.2:50461 -> 192.168.65.1 5857 Query:0 na:c:r:rn 0 <qs:google.com. <A|IN>> <an:> <au:> <ad:>
[11:45:18.192][VpnKit ][Debug ] com.docker.slirp.exe: DNS[5857] Forwarding to 192.168.8.1 (0)
[11:45:18.194][VpnKit ][Debug ] com.docker.slirp.exe: Socket.Datagram.input udp:192.168.65.2:50461-192.168.8.1:53 (DNS[5857]): creating UDP NAT rule
[11:45:18.194][VpnKit ][Debug ] com.docker.slirp.exe: DNS[5857] 192.168.65.2:50461 -> 192.168.65.10 5857 Query:0 na:c:r:rn 0 <qs:google.com. <A|IN>> <an:> <au:> <ad:>
[11:45:18.195][VpnKit ][Debug ] com.docker.slirp.exe: DNS[5857] Forwarding to 192.168.8.1 (1)
[11:45:18.196][VpnKit ][Debug ] com.docker.slirp.exe: DNS[5857] 192.168.65.2:50461 -> 192.168.65.9 5857 Query:0 na:c:r:rn 0 <qs:google.com. <A|IN>> <an:> <au:> <ad:>
[11:45:18.196][VpnKit ][Debug ] com.docker.slirp.exe: DNS[5857] Forwarding to 192.168.8.1 (2(wrapped))
[11:45:18.197][VpnKit ][Debug ] com.docker.slirp.exe: DNS[5aaf] 192.168.65.2:50461 -> 192.168.65.1 5aaf Query:0 na:c:r:rn 0 <qs:google.com. <AAAA|IN>> <an:> <au:> <ad:>
[11:45:18.198][VpnKit ][Debug ] com.docker.slirp.exe: DNS[5aaf] Forwarding to 192.168.8.1 (0)
[11:45:18.198][VpnKit ][Debug ] com.docker.slirp.exe: DNS[5aaf] 192.168.65.2:50461 -> 192.168.65.10 5aaf Query:0 na:c:r:rn 0 <qs:google.com. <AAAA|IN>> <an:> <au:> <ad:>
[11:45:18.199][VpnKit ][Debug ] com.docker.slirp.exe: DNS[5aaf] Forwarding to 192.168.8.1 (1)
[11:45:18.199][VpnKit ][Debug ] com.docker.slirp.exe: DNS[5aaf] 192.168.65.2:50461 -> 192.168.65.9 5aaf Query:0 na:c:r:rn 0 <qs:google.com. <AAAA|IN>> <an:> <au:> <ad:>
[11:45:18.200][VpnKit ][Debug ] com.docker.slirp.exe: DNS[5aaf] Forwarding to 192.168.8.1 (2(wrapped))
[11:45:18.201][VpnKit ][Debug ] com.docker.slirp.exe: Socket.Datagram udp:192.168.65.2:50461-192.168.8.1:53 (DNS[5857]): expiring UDP NAT rule immediately
[11:45:18.201][VpnKit ][Debug ] com.docker.slirp.exe: DNS[5aaf] 192.168.65.2:50461 <- 2(wrapped) (5857 Response:0 na:c:r:ra 0 <qs:google.com. <A|IN>> <an:google.com <IN|147> [A (216.58.194.206)]> <au:> <ad:>)
[11:45:20.695][VpnKit ][Debug ] com.docker.slirp.exe: DNS[5aaf] 192.168.65.2:50461 -> 192.168.65.1 5aaf Query:0 na:c:r:rn 0 <qs:google.com. <AAAA|IN>> <an:> <au:> <ad:>
[11:45:20.696][VpnKit ][Debug ] com.docker.slirp.exe: DNS[5aaf] Forwarding to 192.168.8.1 (0)
[11:45:20.697][VpnKit ][Debug ] com.docker.slirp.exe: Socket.Datagram.input udp:192.168.65.2:50461-192.168.8.1:53 (DNS[5aaf]): creating UDP NAT rule
[11:45:20.698][VpnKit ][Debug ] com.docker.slirp.exe: DNS[5aaf] 192.168.65.2:50461 -> 192.168.65.10 5aaf Query:0 na:c:r:rn 0 <qs:google.com. <AAAA|IN>> <an:> <au:> <ad:>
[11:45:20.701][VpnKit ][Debug ] com.docker.slirp.exe: DNS[5aaf] Forwarding to 192.168.8.1 (1)
[11:45:20.703][VpnKit ][Debug ] com.docker.slirp.exe: DNS[5aaf] 192.168.65.2:50461 -> 192.168.65.9 5aaf Query:0 na:c:r:rn 0 <qs:google.com. <AAAA|IN>> <an:> <au:> <ad:>
[11:45:20.704][VpnKit ][Debug ] com.docker.slirp.exe: DNS[5aaf] Forwarding to 192.168.8.1 (2(wrapped))
[11:45:20.706][VpnKit ][Debug ] com.docker.slirp.exe: Socket.Datagram udp:192.168.65.2:50461-192.168.8.1:53 (DNS[5aaf]): expiring UDP NAT rule immediately
[11:45:20.707][VpnKit ][Debug ] com.docker.slirp.exe: DNS[5aaf] 192.168.65.2:50461 <- 2(wrapped) (5aaf Response:0 na:c:r:ra 0 <qs:google.com. <AAAA|IN>> <an:google.com <IN|145> [AAAA (2607:f8b0:4005:805::200e)]> <au:> <ad:>)
Now, pf-int-cake1.hq.practicefusion.com from within a container:
$ docker run --rm -it alpine sh
/ # ping pf-int-cake1.hq.practicefusion.com
ping: bad address 'pf-int-cake1.hq.practicefusion.com'
This is still expected, we're not on the VPN yet. Here are the logs from this call:
[11:47:20.437][VpnKit ][Debug ] com.docker.slirp.exe: DNS[58a2] 192.168.65.2:38963 -> 192.168.65.1 58a2 Query:0 na:c:r:rn 0 <qs:pf-int-cake1.hq.practicefusion.com. <A|IN>> <an:> <au:> <ad:>
[11:47:20.438][VpnKit ][Debug ] com.docker.slirp.exe: DNS[58a2] Forwarding to 192.168.8.1 (0)
[11:47:20.439][VpnKit ][Debug ] com.docker.slirp.exe: Socket.Datagram.input udp:192.168.65.2:38963-192.168.8.1:53 (DNS[58a2]): creating UDP NAT rule
[11:47:20.440][VpnKit ][Debug ] com.docker.slirp.exe: DNS[58a2] 192.168.65.2:38963 -> 192.168.65.10 58a2 Query:0 na:c:r:rn 0 <qs:pf-int-cake1.hq.practicefusion.com. <A|IN>> <an:> <au:> <ad:>
[11:47:20.441][VpnKit ][Debug ] com.docker.slirp.exe: DNS[58a2] Forwarding to 192.168.8.1 (1)
[11:47:20.442][VpnKit ][Debug ] com.docker.slirp.exe: DNS[58a2] 192.168.65.2:38963 -> 192.168.65.9 58a2 Query:0 na:c:r:rn 0 <qs:pf-int-cake1.hq.practicefusion.com. <A|IN>> <an:> <au:> <ad:>
[11:47:20.443][VpnKit ][Debug ] com.docker.slirp.exe: DNS[58a2] Forwarding to 192.168.8.1 (2(wrapped))
[11:47:20.443][VpnKit ][Debug ] com.docker.slirp.exe: DNS[5afa] 192.168.65.2:38963 -> 192.168.65.1 5afa Query:0 na:c:r:rn 0 <qs:pf-int-cake1.hq.practicefusion.com. <AAAA|IN>> <an:> <au:> <ad:>
[11:47:20.444][VpnKit ][Debug ] com.docker.slirp.exe: DNS[5afa] Forwarding to 192.168.8.1 (0)
[11:47:20.445][VpnKit ][Debug ] com.docker.slirp.exe: DNS[5afa] 192.168.65.2:38963 -> 192.168.65.10 5afa Query:0 na:c:r:rn 0 <qs:pf-int-cake1.hq.practicefusion.com. <AAAA|IN>> <an:> <au:> <ad:>
[11:47:20.445][VpnKit ][Debug ] com.docker.slirp.exe: DNS[5afa] Forwarding to 192.168.8.1 (1)
[11:47:20.446][VpnKit ][Debug ] com.docker.slirp.exe: DNS[5afa] 192.168.65.2:38963 -> 192.168.65.9 5afa Query:0 na:c:r:rn 0 <qs:pf-int-cake1.hq.practicefusion.com. <AAAA|IN>> <an:> <au:> <ad:>
[11:47:20.446][VpnKit ][Debug ] com.docker.slirp.exe: DNS[5afa] Forwarding to 192.168.8.1 (2(wrapped))
[11:47:20.458][VpnKit ][Debug ] com.docker.slirp.exe: Socket.Datagram udp:192.168.65.2:38963-192.168.8.1:53 (DNS[58a2]): expiring UDP NAT rule immediately
[11:47:20.458][VpnKit ][Debug ] com.docker.slirp.exe: DNS[5afa] 192.168.65.2:38963 <- 2(wrapped) (58a2 Response:0 na:c:r:ra 3 <qs:pf-int-cake1.hq.practicefusion.com. <A|IN>> <an:> <au:hq.practicefusion.com <IN|900> [SOA (ns-183.awsdns-22.com,awsdns-hostmaster.amazon.com, 1,7200,900,1209600,86400)]> <ad:>)
[11:47:22.939][VpnKit ][Debug ] com.docker.slirp.exe: DNS[5afa] 192.168.65.2:38963 -> 192.168.65.1 5afa Query:0 na:c:r:rn 0 <qs:pf-int-cake1.hq.practicefusion.com. <AAAA|IN>> <an:> <au:> <ad:>
[11:47:22.940][VpnKit ][Debug ] com.docker.slirp.exe: DNS[5afa] Forwarding to 192.168.8.1 (0)
[11:47:22.940][VpnKit ][Debug ] com.docker.slirp.exe: Socket.Datagram.input udp:192.168.65.2:38963-192.168.8.1:53 (DNS[5afa]): creating UDP NAT rule
[11:47:22.941][VpnKit ][Debug ] com.docker.slirp.exe: DNS[5afa] 192.168.65.2:38963 -> 192.168.65.10 5afa Query:0 na:c:r:rn 0 <qs:pf-int-cake1.hq.practicefusion.com. <AAAA|IN>> <an:> <au:> <ad:>
[11:47:22.942][VpnKit ][Debug ] com.docker.slirp.exe: DNS[5afa] Forwarding to 192.168.8.1 (1)
[11:47:22.942][VpnKit ][Debug ] com.docker.slirp.exe: DNS[5afa] 192.168.65.2:38963 -> 192.168.65.9 5afa Query:0 na:c:r:rn 0 <qs:pf-int-cake1.hq.practicefusion.com. <AAAA|IN>> <an:> <au:> <ad:>
[11:47:22.943][VpnKit ][Debug ] com.docker.slirp.exe: DNS[5afa] Forwarding to 192.168.8.1 (2(wrapped))
[11:47:22.955][VpnKit ][Debug ] com.docker.slirp.exe: Socket.Datagram udp:192.168.65.2:38963-192.168.8.1:53 (DNS[5afa]): expiring UDP NAT rule immediately
[11:47:22.955][VpnKit ][Debug ] com.docker.slirp.exe: DNS[5afa] 192.168.65.2:38963 <- 2(wrapped) (5afa Response:0 na:c:r:ra 3 <qs:pf-int-cake1.hq.practicefusion.com. <AAAA|IN>> <an:> <au:hq.practicefusion.com <IN|898> [SOA (ns-183.awsdns-22.com,awsdns-hostmaster.amazon.com, 1,7200,900,1209600,86400)]> <ad:>)
Connecting to VPN
These log entries showed up when I connected to the VPN:
[12:53:32.906][VpnKit ][Info ] com.docker.slirp.exe: hosts file has bindings for access.practicefusion.com
[12:53:37.956][VpnKit ][Info ] com.docker.slirp.exe: hosts file has bindings for
[12:53:38.354][DnsUpdater ][Info ] Network configuration change detected
[12:53:38.356][PowerShell ][Info ] Run script '$(Find-NetRoute -RemoteIPAddress 8.8.8.8).InterfaceIndex[0]'...
[12:53:38.481][Database ][Info ] Writing com.docker.driver.amd64-linux/slirp/dns=nameserver 192.168.8.1
search hq.practicefusion.com
search patientfusion.com
search practicefusion.com
search hq.practicefusion.com
search practicefusion.net
search patientfusion.local
search ringadoc.com
search patientfusion.net
search hq.practicefusion.com
search pfsc.local
search stg-pfsc.local
search patientfusion.local
nameserver 10.11.79.12
search hq.practicefusion.com
search patientfusion.com
search practicefusion.com
search hq.practicefusion.com
search practicefusion.net
search patientfusion.local
search ringadoc.com
search patientfusion.net
search hq.practicefusion.com
search pfsc.local
search stg-pfsc.local
search patientfusion.local
[12:53:38.641][DataKit ][Info ]
[12:53:38.642][VpnKit ][Info ] com.docker.slirp.exe: updating search domains to patientfusion.local stg-pfsc.local pfsc.local hq.practicefusion.com patientfusion.net ringadoc.com patientfusion.local practicefusion.net hq.practicefusion.com practicefusion.com patientfusion.com hq.practicefusion.com patientfusion.local stg-pfsc.local pfsc.local hq.practicefusion.com patientfusion.net ringadoc.com patientfusion.local practicefusion.net hq.practicefusion.com practicefusion.com patientfusion.com hq.practicefusion.com
[12:53:38.642][VpnKit ][Info ] com.docker.slirp.exe: updating resolvers to nameserver 192.168.8.1#53
[12:53:38.644][VpnKit ][Info ] nameserver 10.11.79.12#53
[12:53:38.645][VpnKit ][Info ] com.docker.slirp.exe: using DNS forwarders on 192.168.8.1#53; 10.11.79.12#53
[12:53:38.642][DataKit ][Info ] +137771873us fs9p [ERROR] dispatcher caught Unix.Unix_error(Unix.EPIPE, "bytes_read", ""): no more requests will be handled
[12:53:38.651][Database ][Info ] Successfully wrote 1 value(s)
[12:53:38.653][DnsUpdater ][Info ] Network configuration change detected
[12:53:38.653][PowerShell ][Info ] Run script '$(Find-NetRoute -RemoteIPAddress 8.8.8.8).InterfaceIndex[0]'...
[12:53:38.713][DnsUpdater ][Info ] Network configuration change detected
[12:53:38.713][PowerShell ][Info ] Run script '$(Find-NetRoute -RemoteIPAddress 8.8.8.8).InterfaceIndex[0]'...
[12:53:39.383][DnsUpdater ][Info ] Network configuration change detected
[12:53:39.384][PowerShell ][Info ] Run script '$(Find-NetRoute -RemoteIPAddress 8.8.8.8).InterfaceIndex[0]'...
Connected to VPN
Again, let's establish that things are working as expected before we try anything in docker.
First, let's ping google.com from the host machine:
$ ping google.com
Pinging google.com [216.58.194.206] with 32 bytes of data:
And let's try an internal name pf-int-cake1.hq.practicefusion.com from the host machine:
$ ping pf-int-cake1.hq.practicefusion.com
Pinging pf-int-cake1.hq.practicefusion.com [10.12.242.151] with 32 bytes of data:
OK! We can resolve both google and pf-int-cake1 successfully from our host machine. The VPN is working, and split-DNS configuration appears to be good.
Now let's try from within docker containers.
First up, google.com from within a container:
$ docker run --rm -it alpine sh
/ # ping google.com
PING google.com (2607:f8b0:4005:808::200e): 56 data bytes
ping: sendto: Network unreachable
Doh! Looks like it resolved something, but it's IPv6 ? Here's the output:
[12:55:03.025][VpnKit ][Debug ] com.docker.slirp.exe: DNS[d769] 192.168.65.2:57020 -> 192.168.65.1 d769 Query:0 na:c:r:rn 0 <qs:google.com. <A|IN>> <an:> <au:> <ad:>
[12:55:03.026][VpnKit ][Debug ] com.docker.slirp.exe: DNS[d769] Forwarding to 192.168.8.1 (0)
[12:55:03.027][VpnKit ][Debug ] com.docker.slirp.exe: Socket.Datagram.input udp:192.168.65.2:57020-192.168.8.1:53 (DNS[d769]): creating UDP NAT rule
[12:55:03.028][VpnKit ][Debug ] com.docker.slirp.exe: DNS[d769] 192.168.65.2:57020 -> 192.168.65.10 d769 Query:0 na:c:r:rn 0 <qs:google.com. <A|IN>> <an:> <au:> <ad:>
[12:55:03.029][VpnKit ][Debug ] com.docker.slirp.exe: DNS[d769] Forwarding to 10.11.79.12 (1)
[12:55:03.030][VpnKit ][Debug ] com.docker.slirp.exe: DNS[d769] 192.168.65.2:57020 -> 192.168.65.9 d769 Query:0 na:c:r:rn 0 <qs:google.com. <A|IN>> <an:> <au:> <ad:>
[12:55:03.031][VpnKit ][Debug ] com.docker.slirp.exe: DNS[d769] Forwarding to 192.168.8.1 (2)
[12:55:03.032][VpnKit ][Debug ] com.docker.slirp.exe: DNS[db51] 192.168.65.2:57020 -> 192.168.65.1 db51 Query:0 na:c:r:rn 0 <qs:google.com. <AAAA|IN>> <an:> <au:> <ad:>
[12:55:03.032][VpnKit ][Debug ] com.docker.slirp.exe: DNS[db51] Forwarding to 192.168.8.1 (0)
[12:55:03.033][VpnKit ][Debug ] com.docker.slirp.exe: DNS[db51] 192.168.65.2:57020 -> 192.168.65.10 db51 Query:0 na:c:r:rn 0 <qs:google.com. <AAAA|IN>> <an:> <au:> <ad:>
[12:55:03.034][VpnKit ][Debug ] com.docker.slirp.exe: DNS[db51] Forwarding to 10.11.79.12 (1)
[12:55:03.034][VpnKit ][Debug ] com.docker.slirp.exe: Socket.Datagram udp:192.168.65.2:57020-192.168.8.1:53 (DNS[d769]): expiring UDP NAT rule immediately
[12:55:03.035][VpnKit ][Debug ] com.docker.slirp.exe: DNS[db51] 192.168.65.2:57020 <- 1 (d769 Response:0 na:c:r:rn 3 <qs:google.com. <A|IN>> <an:> <au:> <ad:>)
[12:55:03.036][VpnKit ][Debug ] com.docker.slirp.exe: DNS[db51] 192.168.65.2:57020 -> 192.168.65.9 db51 Query:0 na:c:r:rn 0 <qs:google.com. <AAAA|IN>> <an:> <au:> <ad:>
[12:55:03.036][VpnKit ][Debug ] com.docker.slirp.exe: DNS[db51] Forwarding to 192.168.8.1 (2)
[12:55:03.037][VpnKit ][Debug ] com.docker.slirp.exe: Socket.Datagram.input udp:192.168.65.2:57020-192.168.8.1:53 (DNS[db51]): creating UDP NAT rule
[12:55:03.042][VpnKit ][Debug ] com.docker.slirp.exe: Socket.Datagram udp:192.168.65.2:57020-192.168.8.1:53 (DNS[db51]): expiring UDP NAT rule immediately
[12:55:03.044][VpnKit ][Debug ] com.docker.slirp.exe: DNS[db51] 192.168.65.2:57020 <- 2 (db51 Response:0 na:c:r:ra 0 <qs:google.com. <AAAA|IN>> <an:google.com <IN|207> [AAAA (2607:f8b0:4005:808::200e)]> <au:> <ad:>)
And finally, trying pf-int-cake1.hq.practicefusion.com inside the container:
/ # ping pf-int-cake1.hq.practicefusion.com
ping: bad address 'pf-int-cake1.hq.practicefusion.com'
This fails too unfortunately. Here are the logs for that query:
[12:56:15.518][VpnKit ][Debug ] com.docker.slirp.exe: DNS[8377] 192.168.65.2:37302 -> 192.168.65.1 8377 Query:0 na:c:r:rn 0 <qs:pf-int-cake1.hq.practicefusion.com. <A|IN>> <an:> <au:> <ad:>
[12:56:15.519][VpnKit ][Debug ] com.docker.slirp.exe: DNS[8377] Forwarding to 192.168.8.1 (0)
[12:56:15.520][VpnKit ][Debug ] com.docker.slirp.exe: Socket.Datagram.input udp:192.168.65.2:37302-192.168.8.1:53 (DNS[8377]): creating UDP NAT rule
[12:56:15.520][VpnKit ][Debug ] com.docker.slirp.exe: DNS[8377] 192.168.65.2:37302 -> 192.168.65.10 8377 Query:0 na:c:r:rn 0 <qs:pf-int-cake1.hq.practicefusion.com. <A|IN>> <an:> <au:> <ad:>
[12:56:15.521][VpnKit ][Debug ] com.docker.slirp.exe: DNS[8377] Forwarding to 10.11.79.12 (1)
[12:56:15.522][VpnKit ][Debug ] com.docker.slirp.exe: DNS[8377] 192.168.65.2:37302 -> 192.168.65.9 8377 Query:0 na:c:r:rn 0 <qs:pf-int-cake1.hq.practicefusion.com. <A|IN>> <an:> <au:> <ad:>
[12:56:15.523][VpnKit ][Debug ] com.docker.slirp.exe: DNS[8377] Forwarding to 192.168.8.1 (2)
[12:56:15.523][VpnKit ][Debug ] com.docker.slirp.exe: DNS[8697] 192.168.65.2:37302 -> 192.168.65.1 8697 Query:0 na:c:r:rn 0 <qs:pf-int-cake1.hq.practicefusion.com. <AAAA|IN>> <an:> <au:> <ad:>
[12:56:15.524][VpnKit ][Debug ] com.docker.slirp.exe: DNS[8697] Forwarding to 192.168.8.1 (0)
[12:56:15.525][VpnKit ][Debug ] com.docker.slirp.exe: DNS[8697] 192.168.65.2:37302 -> 192.168.65.10 8697 Query:0 na:c:r:rn 0 <qs:pf-int-cake1.hq.practicefusion.com. <AAAA|IN>> <an:> <au:> <ad:>
[12:56:15.525][VpnKit ][Debug ] com.docker.slirp.exe: DNS[8697] Forwarding to 10.11.79.12 (1)
[12:56:15.526][VpnKit ][Debug ] com.docker.slirp.exe: DNS[8697] 192.168.65.2:37302 -> 192.168.65.9 8697 Query:0 na:c:r:rn 0 <qs:pf-int-cake1.hq.practicefusion.com. <AAAA|IN>> <an:> <au:> <ad:>
[12:56:15.526][VpnKit ][Debug ] com.docker.slirp.exe: DNS[8697] Forwarding to 192.168.8.1 (2)
[12:56:15.527][VpnKit ][Debug ] com.docker.slirp.exe: Socket.Datagram udp:192.168.65.2:37302-192.168.8.1:53 (DNS[8377]): expiring UDP NAT rule immediately
[12:56:15.528][VpnKit ][Debug ] com.docker.slirp.exe: DNS[8697] 192.168.65.2:37302 <- 2 (8377 Response:0 na:c:r:rn 3 <qs:pf-int-cake1.hq.practicefusion.com. <A|IN>> <an:> <au:> <ad:>)
[12:56:18.021][VpnKit ][Debug ] com.docker.slirp.exe: DNS[8697] 192.168.65.2:37302 -> 192.168.65.1 8697 Query:0 na:c:r:rn 0 <qs:pf-int-cake1.hq.practicefusion.com. <AAAA|IN>> <an:> <au:> <ad:>
[12:56:18.023][VpnKit ][Debug ] com.docker.slirp.exe: DNS[8697] Forwarding to 192.168.8.1 (0)
[12:56:18.025][VpnKit ][Debug ] com.docker.slirp.exe: Socket.Datagram.input udp:192.168.65.2:37302-192.168.8.1:53 (DNS[8697]): creating UDP NAT rule
[12:56:18.028][VpnKit ][Debug ] com.docker.slirp.exe: DNS[8697] 192.168.65.2:37302 -> 192.168.65.10 8697 Query:0 na:c:r:rn 0 <qs:pf-int-cake1.hq.practicefusion.com. <AAAA|IN>> <an:> <au:> <ad:>
[12:56:18.031][VpnKit ][Debug ] com.docker.slirp.exe: DNS[8697] Forwarding to 10.11.79.12 (1)
[12:56:18.033][VpnKit ][Debug ] com.docker.slirp.exe: DNS[8697] 192.168.65.2:37302 -> 192.168.65.9 8697 Query:0 na:c:r:rn 0 <qs:pf-int-cake1.hq.practicefusion.com. <AAAA|IN>> <an:> <au:> <ad:>
[12:56:18.035][VpnKit ][Debug ] com.docker.slirp.exe: DNS[8697] Forwarding to 192.168.8.1 (2)
[12:56:18.037][VpnKit ][Debug ] com.docker.slirp.exe: Socket.Datagram udp:192.168.65.2:37302-192.168.8.1:53 (DNS[8697]): expiring UDP NAT rule immediately
[12:56:18.038][VpnKit ][Debug ] com.docker.slirp.exe: DNS[8697] 192.168.65.2:37302 <- 2 (8697 Response:0 na:c:r:rn 3 <qs:pf-int-cake1.hq.practicefusion.com. <AAAA|IN>> <an:> <au:> <ad:>)
New Diagnostic ID here: 65D06FF4-BA21-452C-9BC6-466F91C0C53A/2016-10-13_12-57-35
from for-win.
docker-robott
commented on August 26, 2024
Closed issues are locked after 30 days of inactivity.
This helps our team focus on active issues.
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.
/lifecycle locked
from for-win.
Related Issues (20)
- Docker Desktop - Unexpected WSL erro HOT 1
- Docker-Desktop Unexpected WSL Error HOT 2
- Uninstaller doesnt complete uninstallation - 4.30.0 (even after running it as admin)
- HTML not rendered in browser
- Docker HOT 1
- Docker Desktop - Unexpected WSL error HOT 2
- Automatic Update Moved Storage Location and Won't let me move back. HOT 3
- Docker Desktop Update Fails to Install After Uninstalling Previous Version on Windows 10 Enterprise HOT 1
- Docker Desktop wsl unexpected error HOT 7
- not runing HOT 1
- Tray icon doesn't disappear until I hover over it.
- Docker Desktop - Unexpected WSL error HOT 1
- Docker Desktop Update breaks MongoDB connection
- Docker diagnositics HOT 2
- Docker Desktop - Unexpected WSL error HOT 3
- Docker Desktop - WSL update failed
- Docker Desktop - WSL Update Failed with Error Code 4294967295 HOT 1
- The same WSL issue everyone is having HOT 1
- can not install Docker 4.30.0 on Windows 10. HOT 1
- Docker not starting HOT 2
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from for-win.