![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
I'm familiar with <draft-klensin-rfc2821bis-10.txt> and understand the importance of using only FQDNs in SMTP exchanges given that "[i]n the case of a top-level domain used by itself in an email address, a single string is used without any dots." What I'm interested in is any reason to proscribe the use of a TLD as a single label hostname (particularly for email addresses) other than the fact that there is software out there that will interpret it incorrectly -
- Lyman On Jul 2, 2008, at 8:07 PM, Bernard Aboba wrote:
Mark Andrews said:"The Internet went to multi-label hostnames ~20 years ago.We added ".ARPA" to all the single label hostnames as partof that process. The only hold over is "localhost" andthat is implemeted locally, not in the global DNS. No sane TLD operator can expect "http://tld" or "user at tld"to work reliably. I suspect there are still mail configuationsaround that will re-write "user at tld" to user at tld.ARPA.Should we be writting a RFC which states that MX and addressrecords SHOULD NOT be added to the apex of a TLD zone?Should we be writting a RFC which states that single labelhostnames/ mail domains SHOULD NOT be looked up "as is" inthe DNS?"Both sound like good ideas to me. _______________________________________________ Ietf mailing list Ietf at ietf.org https://www.ietf.org/mailman/listinfo/ietf
_______________________________________________ Ietf mailing list Ietf at ietf.org https://www.ietf.org/mailman/listinfo/ietf
Note Well: Messages sent to this mailing list are the opinions of the senders and do not imply endorsement by the IETF.