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
Does this issue reproduce with the latest release?
yes
What operating system and processor architecture are you using (go env)?
go env Output
$ go env
GOARCH="amd64"
GOOS="darwin"
What did you do?
Resolving an unexisting domain via a custom DNS server returns an error message with the host DNS server address instead of custom.
When I tried to resolve the domain, that exists on my local network DNS server but doesn't exist on custom (external in my case), I got the same error. That's why I assume that go correctly uses custom DNS, but when it generates a message, it ignores configured resolver server
What version of Go are you using (
go version
)?Does this issue reproduce with the latest release?
yes
What operating system and processor architecture are you using (
go env
)?go env
OutputWhat did you do?
Resolving an unexisting domain via a custom DNS server returns an error message with the host DNS server address instead of custom.
When I tried to resolve the domain, that exists on my local network DNS server but doesn't exist on custom (external in my case), I got the same error. That's why I assume that go correctly uses custom DNS, but when it generates a message, it ignores configured resolver server
What did you expect to see?
panic: lookup manager.pls.pbank.com.ua on 1.1.1.1:53: no such host
What did you see instead?
panic: lookup manager.pls.pbank.com.ua on 192.168.1.1:53: no such host
The text was updated successfully, but these errors were encountered: