On Mon, May 18, 2009 at 08:47:09PM -0700, Scott Haneda wrote:
>> Use example.com, example.net, example.org, etc. Or use an impossible name
>> like mydomain.tld, foobar.tld, &c. when obfuscating. Oh, and obfuscating
>> on this list is generally a waste of time and makes it harder for people
>> to help you.
>
> Glad you brought this up, often times I am using example.com and then
> ns.example.com and imap.example.com and want to refer to something else
> outside of example.com.
Yes, the point is a bit pedantic in this context. On the other hand
the RFC gives you a lot more rope:
- example TLD and all sub-domains.
- example.com 2LD and all sub-domains
- example.org 2LD and all sub-domains
- example.net 2LD and all sub-domains
> I am pretty sure there is even an RFC that states
http://tools.ietf.org/html/rfc2606
> to use example.com. However, when you want to show a two sided problem,
> you need another, using second.tld is a nice way to do that, so thanks.
No need to over-react, that gets out of hand fast...
> It would be interesting to see some data on 208.77.188.166 (example.com A
> record) to see just what type of traffic they do get.
This is IANA reserved address space, if this is not a black-hole, the
packets received are used for research... See also:
http://tools.ietf.org/html/rfc3330
192.0.2.0/24 - This block is assigned as "TEST-NET" for use in
documentation and example code. It is often used in conjunction with
domain names example.com or example.net in vendor and protocol
documentation. Addresses within this block should not appear on the
public Internet.
http://tools.ietf.org/html/rfc3849
To reduce the likelihood of conflict and confusion when relating
documented examples to deployed systems, an IPv6 unicast address
prefix is reserved for use in examples in RFCs, books, documentation,
and the like. Since site-local and link-local unicast addresses have
special meaning in IPv6, these addresses cannot be used in many
example situations. The document describes the use of the IPv6
address prefix 2001:DB8::/32 as a reserved prefix for use in
documentation.
Now please return to the original topic of this thread or start a new one.
--
Viktor.
Disclaimer: off-list followups get on-list replies or get ignored.
Please do not ignore the "Reply-To" header.
To unsubscribe from the postfix-users list, visit
http://www.postfix.org/lists.html or click the link below:
<mailto:majord...@postfix.org?body=unsubscribe%20postfix-users>
If my response solves your problem, the best way to thank me is to not
send an "it worked, thanks" follow-up. If you must respond, please put
"It worked, thanks" in the "Subject" so I can delete these quickly.
