Example.com Has Changed 109
An anonymous reader writes "The familiar example.com domain, reserved for private testing, has been updated. Visiting the domain in a web browser no longer displays any content; instead, visitors are redirected to an explanatory page on IANA's website at iana.org/domains/example/. Other example domains such as example.net are also affected. Is this a bad change? Will the redirect cause problems for anybody?"
No (Score:5, Informative)
GET / HTTP/1.1
Host: www.example.com
HTTP/1.0 302 Found
Location: http://www.iana.org/domains/example/ [iana.org]
Server: BigIP
Connection: Keep-Alive
Content-Length: 0
If that breaks your program, you're doing it wrong.
Re:really? (Score:5, Informative)
It may not matter very much, but it definitely is "news for nerds", in that nerds are the only one who would even notice. They never said it was "news for nerds && stuff that matters".
Re:really? (Score:5, Informative)
I don't know, it is pretty Earth shattering news.
I don't think i will be able to sleep at work today because of it....
Re:No (Score:5, Informative)
It won't break your program, but it might break your example. I've seen HTTP tutorials that show using telnet to connect to example.com, and getting a response. Now the response is different, so anyone who tries the example will see a redirect instead of a content reply.
It's not a serious problem, but it may cause a small amount of confusion for a tiny group of people.
Re:really? (Score:2, Informative)
Yes it is. I'm a nerd and never knew that example.com etc.. were reserved by iana, I thought it was interesting.
Furthermore unlike MOST slashdot summaries, it wasn't ridiculously sensationalistic and misleading.
Re:For documentation purposes (Score:5, Informative)
Example.com at least isn't a change in that scenario because it used to resolve to a specific server. Now that it resolves with a redirect, I don't see much difference at the DNS layer.
Re:you might have bigger problem (Score:3, Informative)
The test suite of Darcs [darcs.net] needs a domain that doesn't exist. It used to use example.com for that purpose, which now fails:
".example" is recommended for use in documentation or as examples.
".invalid" is intended for use in online construction of domain names that are sure to be invalid and which it is obvious at a glance are invalid.
Guess they should read the rfc.