On Jun 7, 2007, at 9:57 PM, Mark Andrews wrote:
I also concur with the various protests against using . for the
RNAME,
and would suggest instead "nobody.localhost." along with a ref to
2606. That should be sufficiently clear to any human who looks at it,
and also meets the goal of not providing any useful data to a spam
bot.
Not "nobody.invalid."?
[EMAIL PROTECTED] is likely to be a real mailbox.
[EMAIL PROTECTED] should bounce.
It seems that a domain of "invalid" may not be recognized by its name
alone as being invalid. How long will it be before DNS servers and
applications reliably recognize this domain as being invalid?
There might be a desire in some protocols to publish records that
points to an invalid hostname. This could be their method to
indicate a type of non-existence. However, this might backfire as
being seen as being a valid hostname instead. Applications may also
attempt to discover a name server for this domain. What portion of
this traffic will be mitigated?
-Doug
_______________________________________________
DNSOP mailing list
DNSOP@ietf.org
https://www1.ietf.org/mailman/listinfo/dnsop
