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 I update/set a the DNS resolver to a custom address the error when host can't connect or couldn't resolve is using the incorrect DNS server address in the response. Example: play.golang.org link: https://play.golang.org/p/LmTM-eOy3q-
What did you expect to see?
I see the error message indicating that it failed with the provisioned DNS server. I am assuming this is just invalid error message but not an issue with golang not using the correct DNS server.
What did you see instead?
It is using the default DNS server (likely configured through DSCP) in the error message instead of 8.8.8.8.
from default resolver
from default resolver
from default resolver
from default resolver
from default resolver
from default resolver
from default resolver
from default resolver
from default resolver
from default resolver
from default resolver
from default resolver
addr: []
err: lookup google.com on 169.254.169.254:53: dial udp 8.8.8.8:53: connect: no route to host
from default resolver
from default resolver
from default resolver
from default resolver
from default resolver
from default resolver
from default resolver
from default resolver
from default resolver
from default resolver
from default resolver
from default resolver
addr: []
err: lookup gafwefjawioefjoawjfoaewif.com on 169.254.169.254:53: dial udp 8.8.8.8:53: connect: no route to host
from custom resolver
from custom resolver
from custom resolver
from custom resolver
from custom resolver
from custom resolver
from custom resolver
from custom resolver
from custom resolver
from custom resolver
from custom resolver
from custom resolver
addr: []
err: lookup google.com on 169.254.169.254:53: dial udp 8.8.8.8:53: connect: no route to host
from custom resolver
from custom resolver
from custom resolver
from custom resolver
from custom resolver
from custom resolver
from custom resolver
from custom resolver
from custom resolver
from custom resolver
from custom resolver
from custom resolver
addr: []
err: lookup gafwefjawioefjoawjfoaewif.com on 169.254.169.254:53: dial udp 8.8.8.8:53: connect: no route to host
The text was updated successfully, but these errors were encountered:
What version of Go are you using (
go version
)?go1.14.13
Does this issue reproduce with the latest release?
Yes. At least the latest on go playgound
What operating system and processor architecture are you using (
go env
)?go env
OutputWhat did you do?
If I update/set a the DNS resolver to a custom address the error when host can't connect or couldn't resolve is using the incorrect DNS server address in the response. Example: play.golang.org link: https://play.golang.org/p/LmTM-eOy3q-
What did you expect to see?
I see the error message indicating that it failed with the provisioned DNS server. I am assuming this is just invalid error message but not an issue with golang not using the correct DNS server.
What did you see instead?
It is using the default DNS server (likely configured through DSCP) in the error message instead of 8.8.8.8.
The text was updated successfully, but these errors were encountered: