<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class=""><div><blockquote type="cite" class=""><div class="">On 29.04.2016 г., at 23:34, John Levine <<a href="mailto:johnl@taugh.com" class="">johnl@taugh.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class=""><br class="">RFC 1912 says:<br class=""><br class=""> Don't go overboard with CNAMEs. Use them when renaming hosts, but<br class=""> plan to get rid of them (and inform your users). However CNAMEs are<br class=""> useful (and encouraged) for generalized names for servers -- `ftp'<br class=""> for your ftp server, `www' for your Web server, `gopher' for your<br class=""> Gopher server, `news' for your Usenet news server, etc.<br class=""><br class=""></div></div></blockquote><br class=""></div><div>Sigh.</div><div><br class=""></div><div>We would not have had this discussion, if people were happy to type <a href="http://www.example.com" class="">www.example.com</a> in their browser, instead of <a href="http://example.com" class="">example.com</a>.</div><div><br class=""></div><div>If enough people were able to say NO, the world would be much better place...</div><div><br class=""></div><div>Daniel</div><br class=""></body></html>