You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If one of the name servers in the /etc/resolv.conf file is not working, then dns name resolution that occurs within a container running, for example, fnproject/go:dev, fails even if the other name servers in the /etc/resolv.conf file are able to resolve host names.
The failure appears to be caused by the getaddrinfo function: it aborts the processing as soon as it receives the error related to the faulty name server. This is an excerpt of the system trace generated by the address:
socket(AF_INET, SOCK_DGRAM|SOCK_CLOEXEC|SOCK_NONBLOCK, IPPROTO_IP) = 3
bind(3, {sa_family=AF_INET, sin_port=htons(0), sin_addr=inet_addr(“0.0.0.0”)}, 16) = 0
sendto(3, “\276!\1\0\0\1\0\0\0\0\0\0\16my-proxy\2us\6o”..., 46, MSG_NOSIGNAL, {sa_family=AF_INET, sin_port=htons(53), sin_addr=inet_addr(“A.B.C.D”)}, 16) = 46
sendto(3, “\276!\1\0\0\1\0\0\0\0\0\0\16my-proxy\2us\6o”..., 46, MSG_NOSIGNAL, {sa_family=AF_INET, sin_port=htons(53), sin_addr=inet_addr(“E.F.G.H”)}, 16) = 46
sendto(3, “\276!\1\0\0\1\0\0\0\0\0\0\16my-proxy\2us\6o”..., 46, MSG_NOSIGNAL, {sa_family=AF_INET, sin_port=htons(53), sin_addr=inet_addr(“I.J.K.L”)}, 16) = 46
sendto(3, “\300p\1\0\0\1\0\0\0\0\0\0\16my-proxy\2us\6o”..., 46, MSG_NOSIGNAL, {sa_family=AF_INET, sin_port=htons(53), sin_addr=inet_addr(“A.B.C.D”)}, 16) = 46
sendto(3, “\300p\1\0\0\1\0\0\0\0\0\0\16my-proxy\2us\6o”..., 46, MSG_NOSIGNAL, {sa_family=AF_INET, sin_port=htons(53), sin_addr=inet_addr(“E.F.G.H”)}, 16) = 46
sendto(3, “\300p\1\0\0\1\0\0\0\0\0\0\16my-proxy\2us\6o”..., 46, MSG_NOSIGNAL, {sa_family=AF_INET, sin_port=htons(53), sin_addr=inet_addr(“I.J.K.L”)}, 16) = 46
poll([{fd=3, events=POLLIN}], 1, 2500) = 1 ([{fd=3, revents=POLLIN}])
recvfrom(3, “\276!\201\203\0\1\0\0\0\1\0\0\16my-proxy\2us\6o”..., 512, 0, {sa_family=AF_INET, sin_port=htons(53), sin_addr=inet_addr(“I.J.K.L”)}, [16]) = 111
recvfrom(3, “\300p\201\203\0\1\0\0\0\1\0\0\16my-proxy\2us\6o”..., 512, 0, {sa_family=AF_INET, sin_port=htons(53), sin_addr=inet_addr(“I.J.K.L”)}, [16]) = 111
close(3) = 0
write(2, “wget: bad address ’my-proxy”..., 52wget: bad address ‘my-proxy.com:80’
) = 52
The text was updated successfully, but these errors were encountered:
If one of the name servers in the /etc/resolv.conf file is not working, then dns name resolution that occurs within a container running, for example, fnproject/go:dev, fails even if the other name servers in the /etc/resolv.conf file are able to resolve host names.
The failure appears to be caused by the getaddrinfo function: it aborts the processing as soon as it receives the error related to the faulty name server. This is an excerpt of the system trace generated by the address:
socket(AF_INET, SOCK_DGRAM|SOCK_CLOEXEC|SOCK_NONBLOCK, IPPROTO_IP) = 3
bind(3, {sa_family=AF_INET, sin_port=htons(0), sin_addr=inet_addr(“0.0.0.0”)}, 16) = 0
sendto(3, “\276!\1\0\0\1\0\0\0\0\0\0\16my-proxy\2us\6o”..., 46, MSG_NOSIGNAL, {sa_family=AF_INET, sin_port=htons(53), sin_addr=inet_addr(“A.B.C.D”)}, 16) = 46
sendto(3, “\276!\1\0\0\1\0\0\0\0\0\0\16my-proxy\2us\6o”..., 46, MSG_NOSIGNAL, {sa_family=AF_INET, sin_port=htons(53), sin_addr=inet_addr(“E.F.G.H”)}, 16) = 46
sendto(3, “\276!\1\0\0\1\0\0\0\0\0\0\16my-proxy\2us\6o”..., 46, MSG_NOSIGNAL, {sa_family=AF_INET, sin_port=htons(53), sin_addr=inet_addr(“I.J.K.L”)}, 16) = 46
sendto(3, “\300p\1\0\0\1\0\0\0\0\0\0\16my-proxy\2us\6o”..., 46, MSG_NOSIGNAL, {sa_family=AF_INET, sin_port=htons(53), sin_addr=inet_addr(“A.B.C.D”)}, 16) = 46
sendto(3, “\300p\1\0\0\1\0\0\0\0\0\0\16my-proxy\2us\6o”..., 46, MSG_NOSIGNAL, {sa_family=AF_INET, sin_port=htons(53), sin_addr=inet_addr(“E.F.G.H”)}, 16) = 46
sendto(3, “\300p\1\0\0\1\0\0\0\0\0\0\16my-proxy\2us\6o”..., 46, MSG_NOSIGNAL, {sa_family=AF_INET, sin_port=htons(53), sin_addr=inet_addr(“I.J.K.L”)}, 16) = 46
poll([{fd=3, events=POLLIN}], 1, 2500) = 1 ([{fd=3, revents=POLLIN}])
recvfrom(3, “\276!\201\203\0\1\0\0\0\1\0\0\16my-proxy\2us\6o”..., 512, 0, {sa_family=AF_INET, sin_port=htons(53), sin_addr=inet_addr(“I.J.K.L”)}, [16]) = 111
recvfrom(3, “\300p\201\203\0\1\0\0\0\1\0\0\16my-proxy\2us\6o”..., 512, 0, {sa_family=AF_INET, sin_port=htons(53), sin_addr=inet_addr(“I.J.K.L”)}, [16]) = 111
close(3) = 0
write(2, “wget: bad address ’my-proxy”..., 52wget: bad address ‘my-proxy.com:80’
) = 52
The text was updated successfully, but these errors were encountered: