2/6/2024 0 Comments Downloading DNSLookupView 1.12TCP Resolver support was added to libnetwork in January and tagged in v0.8.0-dev.2: /docker/libnetwork Adding TCP listener for embedded DNS Signed-off-by: Madhu Venugopal What that is material to the cause of the truncated EDNS UDP packets, it is not as much of a problem as Docker’s embedded DNS server running at 192.168.65.1 doesn’t seem to be listening for DNS queries via TCP. I’m not quite sure why the results are being truncated as the resolver for my laptop has a max-udp-size and edns-udp-size of 4096. If I change the DNS server to 8.8.8.8, I do not have a problem: moby:~# cat /etc/nfĪ canonical name = .io.Į.io canonical name = .com. When I am in the moby instance, I can not resolve with the default settings:.Alpine 3.4 does not have a problem with truncated issues on its own, so I’m guessing that the main issue here is lack of full EDNS/TCP support in the embedded docker DNS server, which seems to cause an issue when issuing a docker login/pull or anything else asking to resolve since the record seems to be longer than the docker embedded DNS server can handle.On my network, I am getting EDNS truncated responses back which should cause the DNS resolver to failover to TCP queries.The error that I get is a failure to connect to the embedded DNS server in docker via TCP.Previous versions of moby on my network do not have the issue This has something to do with the EDNS record sizes returned for and the new Alpine 3.4 based moby image.So I’ve done a bit of research on this today (that is most of my day has been taken up in researching this).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |