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
As far as I can tell, there's no reason for a forwarding server not to write a truncated message back to the client: forwarding.go
The same logic in the stub server does not treat ErrTruncated this way: stub.go
Context:
Kubernetes/kube-dns: a reverse lookup with host against a kube-dns pod fails (the reverse record is not held locally). The same lookup specifying TCP succeeded. Logs show:
I0601 21:44:11.499737 1 logs.go:41] skydns: failure to forward request "dns: failed to unpack truncated message"
At time of failed query.
The text was updated successfully, but these errors were encountered:
As far as I can tell, there's no reason for a forwarding server not to write a truncated message back to the client: forwarding.go
The same logic in the stub server does not treat
ErrTruncated
this way: stub.goContext:
Kubernetes/kube-dns: a reverse lookup with
host
against a kube-dns pod fails (the reverse record is not held locally). The same lookup specifying TCP succeeded. Logs show:At time of failed query.
The text was updated successfully, but these errors were encountered: