Whereas I don't disagree here, it does break how DNS is supposed to work. A client machine can 'belong' to a DNS namespace, e.g. mycorp.com. Once it does, the

Whereas I don't disagree here, it does break how DNS is supposed to work. A client machine can 'belong' to a DNS namespace, e.g. mycorp.com. Once it does, the DNS resolver should append the namespace automatically onto any non qualified DNS query. So looking up 'server01' would automatically try to resolve 'server01.mycorp.com'. Therefore in a browser, entering 'https://google' https://google' in the address bar should result in a DNS resolution attempt of 'google.mycorp.com'. However, [almost] all browsers, now override that, and prepend 'www.' and append '.com' to any unqualified address BEFORE it hits DNS. If you drop the 'https://' https://' the browser assumes it's a search query and just sends it off to the default search engine. It's another example of browser providers riding roughshod over established standards under the guise of 'ease of use'.