chromium / badssl.com

:lock: Memorable site for testing clients against bad SSL configs.
https://badssl.com
Apache License 2.0
2.78k stars 186 forks source link

no-common-name.badssl.com cannot be resolved to an IP address #481

Closed c0r0n3r closed 2 years ago

c0r0n3r commented 2 years ago

Checked with the following commands:

$ dig @1.1.1.1 -t A +short no-common-name.badssl.com
$ dig @8.8.8.8 -t A +short no-common-name.badssl.com
$ dig @1.1.1.1 -t AAAA +short no-common-name.badssl.com
$ dig @8.8.8.8 -t AAAA +short no-common-name.badssl.com    
lgarron commented 2 years ago

Hmm, I'm also not able to resolve this.

@christhompson, any ideas? We haven't had issues with any of the cert issues affecting DNS resolution, but who knows.

christhompson commented 2 years ago

I think it should be working now.

I'd been testing some ACME DNS challenges which I think might have interacted badly with resolution for this subdomain in an unexpected way. I've deleted those records for now, and the hostname appears to be resolving again.