crypto/x509: TestPlatformVerifier is failing on windows-amd64-longtest

[heschi]

https://build.golang.org/log/296b04ad40e69dc38abad33a8d6ee7ffcb03014c

--- FAIL: TestPlatformVerifier (0.19s)
    root_windows_test.go:77: tls connection failed: dial tcp: lookup wrong.host.badssl.com: getaddrinfow: This is usually a temporary error during hostname resolution and means that the local server did not receive a response from an authoritative server.

No idea what's going wrong, I can resolve the host just fine from my home network but not from my Google workstation. This is a release blocker because the release runs the Windows long tests.

[heschi]

cc @FiloSottile @rolandshoemaker

[heschi]

cc @golang/release

[hopehook]

I can not resolve the host of badssl.com, is it matter？

chromium/badssl.com#500

[bcmills]

This is a release blocker because the release runs the Windows long tests.

It's not just that. We rely heavily on the windows-amd64-longtest builder for testing numerous changes, since most of the Go team isn't developing natively on Windows machines day-to-day.

[gopherbot]

Change https://go.dev/cl/397478 mentions this issue: crypto/x509: skip getaddrinfow errors for "wrong.host.badssl.com"

[heschi]

It looks like badssl.com is completely gone. It's a google project, ish... https://github.com/chromium/badssl.com. Let's see what I can find out internally.

[rolandshoemaker]

It's back up, looks like the DNS was just funky for a while.

[heschi]

Indeed. Not sure how I missed chromium/badssl.com#500.

[gopherbot]

Change https://go.dev/cl/397594 mentions this issue: [release-branch.go1.18] crypto/x509: skip WSATRY_AGAIN errors when dialing badssl.com subdomains