Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

net: DNS lookup on Windows returns "server misbehaving" #70191

Closed
piclemx opened this issue Nov 5, 2024 · 5 comments
Closed

net: DNS lookup on Windows returns "server misbehaving" #70191

piclemx opened this issue Nov 5, 2024 · 5 comments
Labels
OS-Windows WaitingForInfo Issue is not actionable because of missing required information, which needs to be provided.

Comments

@piclemx
Copy link

piclemx commented Nov 5, 2024

Go version

1.23

Output of go env in your module/workspace:

CGO_ENABLED=1 
GOOS=windows 
GOARCH=amd64 
CC=x86_64-w64-mingw32-gcc

What did you do?

We did upgrade one of CLI to go 1.23 and we started to get this

Simple HTTP call to a service result every time with an dial tcp: lookup DNS on IP:53: server misbehaving

That service is working when using the browser or just a simple curl command.

What did you see happen?

dial tcp: lookup DNS on IP:53: server misbehaving

What did you expect to see?

I was expecting that this will do a normal http call has before and just return back the response from the backend.

@gabyhelp
Copy link

gabyhelp commented Nov 5, 2024

Related Issues and Documentation

(Emoji vote if this was helpful or unhelpful; more detailed feedback welcome in this discussion.)

@piclemx
Copy link
Author

piclemx commented Nov 5, 2024

Downgrading to go 1.22 make everything works again

@ianlancetaylor ianlancetaylor changed the title issue resolving DNS on Windows net: DNS lookup on Windows returns "server misbehaving" Nov 5, 2024
@ianlancetaylor
Copy link
Contributor

This happens when the Go program receives a DNS packet with a response code that is neither NoError nor NXDomain. It would help to see a dump of the DNS packets, if possible. It's hard to see why this change between 1.22 and 1.23, though.

One thing you could try is setting GODEBUG=netedns0=0 in the environment.

CC @golang/windows

@seankhliao seankhliao added the WaitingForInfo Issue is not actionable because of missing required information, which needs to be provided. label Nov 5, 2024
@piclemx
Copy link
Author

piclemx commented Nov 5, 2024

Ok, let me check tomorrorw.

@seankhliao seankhliao added WaitingForInfo Issue is not actionable because of missing required information, which needs to be provided. and removed WaitingForInfo Issue is not actionable because of missing required information, which needs to be provided. labels Nov 6, 2024
@gopherbot
Copy link
Contributor

Timed out in state WaitingForInfo. Closing.

(I am just a bot, though. Please speak up if this is a mistake or you have the requested information.)

@gopherbot gopherbot closed this as not planned Won't fix, can't repro, duplicate, stale Dec 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
OS-Windows WaitingForInfo Issue is not actionable because of missing required information, which needs to be provided.
Projects
None yet
Development

No branches or pull requests

5 participants