net: LookupNS doesn't chase through CNAMEs #44199
Open
Labels
Comments
is it consistent in which domains fail and can you give an example of a failing domain? |
@seankhliao I send you PM (twitter) with real domain name. |
sorry closed by error. |
So |
@seankhliao temporary I workaround this scenarios checking CNAME when LookupNS return "no such host", but now I have another set of domains on LookupCNAME returns "no such host" too, but dig cname host works properly:
One more time test int with diferent solvers:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What version of Go are you using (
go version
)?go1.13 darwin/amd64
Does this issue reproduce with the latest release?
yes
What operating system and processor architecture are you using (
go env
)?macos and alpine container
What did you do?
I see related issues with cgo/go/cgo+1 resolvers but:
What did you expect to see?
ghs.googlehosted.com.
What did you see instead?
lookup _acme-challenge.xxxxx.cat on 192.168.50.1:53: no such host
it works fine in most cases, but not in some cases(domains) and I don't understand why.
I have the complete code running in an alpine container within a kubernetes cluster, so I rule out that it is a problem with my local dns solver.
Note: Adding net.LookupCNAME when LookupNS return error I can see the expected result. lookupNS not following CNAME? is the expected behavior?
The text was updated successfully, but these errors were encountered: