Scott Haneda a écrit : > On May 18, 2009, at 8:08 PM, LuKreme wrote: > >> On 17-May-2009, at 19:44, Carlos Williams wrote: >>> u...@mail.myserver.com >> >> myserver.com is a real domain name. Is it YOUR domain name? Somehow I >> doubt it. > > Thank you for pointing this out. I feel bad for anyone at domain, > company, foo, bar, foobar .com etc at least once day. > >> 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. I am pretty sure there is even an RFC that > states 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. >
if you want many domains, just use .example (joe.example, jim.example, jack.example, ... etc). > 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. probably less than reverse DNS queries for private IPs...
