ICANN Considers Using '127.0.53.53' To Tackle DNS Namespace Collisions 164
angry tapir writes "As the number of top-level domains undergoes explosive growth, the Internet Corporation for Assigned Names and Numbers (ICANN) is studying ways to reduce the risk of traffic intended for internal network destinations ending up on the Internet via the Domain Name System. Proposals in a report produced on behalf of ICANN include preventing .mail, .home and .corp ever being Internet TLDs; allowing the forcible de-delegation of some second-level domains in emergencies; and returning 127.0.53.53 as an IP address in the hopes that sysadmins will flag and Google it."
Re:hacky (Score:5, Funny)
Re:hacky (Score:5, Funny)
ICANT think of anything better.
ICANN!
Re:resolv.conf (Score:2, Funny)
I'm using MSDOS, you insensitive clod!
Re: Obsolete (Score:1, Funny)
Boy, boy, stop fighting with yourself.
Re:Those wondering why 53.53 (Score:3, Funny)
127.0.53.53.... why not 127.0.42.42? (Score:5, Funny)
>ping answer.to.the.ultimate.question.of.life.the.universe.and.everything
Pinging 127.0.42.42 with 32 bytes of data:
Reply from 127.0.42.42: bytes=32 time=2ms TTL=249
Reply from 127.0.42.42: bytes=32 time1ms TTL=249
Reply from 127.0.42.42: bytes=32 time=1ms TTL=249
Reply from 127.0.42.42: bytes=32 time1ms TTL=249
Ping statistics for 127.0.42.42:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = eternity, Average = ask Deep Thought
Re:STOP (Score:5, Funny)
I know a few people who have conspired to tell others that the nontraditional domains are like 1-900 phone numbers and when you use them, you will get a bill from your ISP.