<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="">This is not an UI issue at all. It is actually an issue of bending under pressure. “users are always right” is an easy excuse, but never the best. Users do what is possible.<div class=""><br class=""></div><div class=""><div class="">The SRV records essentially solve the same issue. But for SRV to be successful, the DNS protocol should be more strict.</div><div class="">If we would not allow for say, A records at the apex, then people would use SRV instead. Of course, it is too late to disallow A records at the apex — as everyone is convinced by now, that DNS is supposed to work that way.</div><div class=""><br class=""></div><div class="">I know, I know… it is appropriate to use <a href="http://example.com" class="">EXAMPLE.COM</a> as name server name, “because the glue is already there”….</div><div class=""><br class=""></div><div class="">Daniel</div><div class=""><br class=""><div><blockquote type="cite" class=""><div class="">On 4.05.2016 г., at 17:39, John R Levine <<a href="mailto:johnl@taugh.com" class="">johnl@taugh.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class=""><blockquote type="cite" class="">We would not have had this discussion, if people were happy to type <a href="http://www.example.com" class="">www.example.com</a> <<a href="http://www.example.com/" class="">http://www.example.com/</a>> in their browser, instead of <a href="http://example.com" class="">example.com</a> <<a href="http://example.com/" class="">http://example.com/</a>>.<br class=""></blockquote><br class=""><blockquote type="cite" class="">If enough people were able to say NO, the world would be much better place...<br class=""></blockquote><br class="">Blaming the users for poor UI design is an ancient tradition in the computer business, but it's never been very productive.<br class=""><br class="">We also would not have this problem if sometime during the past 20 years we made our applications use SRV records since it solves nearly all of the problems that people are trying to address with funky CNAMEs without putting different names in the UI.<br class=""><br class="">Regards,<br class="">John Levine, <a href="mailto:johnl@taugh.com" class="">johnl@taugh.com</a>, Taughannock Networks, Trumansburg NY<br class="">Please consider the environment before reading this e-mail.<br class=""></div></div></blockquote></div><br class=""></div></div></body></html>