Comment 7 for bug 1968719

FWIW the reason this is in DNS is because there's a DNS wildcard so that per-country domain names work.

These of course also only work over http, not https.

What's particularly strange about the DuckDuckGo results, now that I've thought about it, is that they return https://www.releases.ubuntu.com as a result when that URL would always have returned https errors for them also. So they aren't validating https certificate names?

I've asked our IS team about the possibility of a wildcard SSL cert to go with the wildcard DNS names, we'll see what they come up with.

In the meantime I've also added a rel="canonical" link to the html on the site, which may hint to DuckDuckGo the correct URL to return in searches. (Has not yet had an effect there.)