Talk:Example.com

From Wikipedia, the free encyclopedia
Jump to: navigation, search
WikiProject Computing / Websites  
WikiProject icon This article is within the scope of WikiProject Computing, a collaborative effort to improve the coverage of computers, computing, and information technology on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.
 ???  This article has not yet received a rating on the project's quality scale.
 ???  This article has not yet received a rating on the project's importance scale.
Taskforce icon
This article is supported by WikiProject Websites.
 

Down?[edit]

Is it just me, or have example.com, example.net, and example.org gone down? – Minh Nguyễn (talk, contribs) 23:18, 26 February 2006 (UTC)

According to the Wayback Machine it seems to have happened in 2005 (com, net, org). Not simultaneously for all of them, though. Bromskloss 09:37, 18 April 2006 (UTC)
=/ Surely this is not a good thing, long ago as it may have happened. Shouldn't there be.... someone, who should deal with this? --Jeremy Banks 12:51, 7 June 2006 (UTC)
Interesting. The sites server still respond to pings. --Jeremy Banks 22:28, 24 June 2006 (UTC)
RFC 2606 (you can read it, it's short) does not say that the mentioned addresses should respond with a web page (nor are they required to respond in any other way). On a side note, "example.com", "example.net", "example.org", "www.example.com", "www.example.net" and "www.example.org" all resolve to the same IP address, namely "192.0.34.166". —Bromskloss 10:12, 26 June 2006 (UTC)
They're up again. —Bromskloss 16:31, 9 November 2006 (UTC)
Down again! -- Flutefluteflute Talk Contributions 11:59, 22 December 2006 (UTC)

This must have been some ICANN employee who has taken them down... Last few lines of a traceroute to www.example.com:


18   207 ms   208 ms   210 ms  xe-7-3.r00.lsanca03.us.bb.gin.ntt.net [129.250.4
.238]
19   192 ms   192 ms   192 ms  198.172.117.162
20   195 ms   192 ms   192 ms  gr-1-m7i-e-1-3.icann.org [207.151.118.18]
21   191 ms   193 ms   194 ms  cs-1-bi4k-e-1-1.icann.org [192.0.33.245]
22   199 ms   192 ms   194 ms  www.example.com [192.0.34.166]

Mbimmler 16:59, 2 January 2007 (UTC)

Contacted ICANN to get more information about this. Mbimmler 17:21, 2 January 2007 (UTC)

And up again. Mbimmler 14:03, 3 January 2007 (UTC)

example.org redirects to porn :([edit]

And that sucks! Here I was, adding an example link, and it gets reverted. OK, I undo the revert and think "stupid bot", well I then copy and paste the link, and I get porn!

Needless to say the link is now Wikipeida rather then example.org

example.com still doesn't work either. AFA http://revleft.com 23:48, 18 March 2007 (UTC)

It's fine here. (Points to 192.0.34.166, which doesn't have a web server running, but that's not that important). Perhaps your computer is infected, or your ISP is ripping you off? –EdC 20:24, 19 March 2007 (UTC)
bah. Now it isn't. It was only example.org and not example.com or example.net (these two not resolving). But now, none of them resolve. I guess that bit can be removed now. I'll get onto it. AFA http://revleft.com 15:13, 20 March 2007 (UTC) (hah I remembered to sign this time you stupid bot!)
Strictly speaking, they do resolve (to 192.0.34.166), it's just that there isn't a web server at that address to respond to connection requests. Weird about the porn thing, though; it does happen that web addresses get hijacked, but I'm surprised that someone would go to the trouble of hijacking example.org. –EdC 23:05, 20 March 2007 (UTC)
I'll believe you about that whole resolving thing. And I agree that it is weird that someone would hijack example.org AFA http://www.revleft.com

The IP address should not be included in the article[edit]

1) It's not relevant: the RFC is about the reservation of the name; the IP address is incidental information

2) It's subject to change: It's already changed once before, and it will probably change again in the future. Anything could happen to it: it might change to a different IP, it might resolve to IPv6 in addition to IPv4, it might resolve to multiple IPs, it might not resolve to *any* IP (since there is no requirement that a DNS entry have an A or AAAA record), or it might not even exist in DNS in the future (since the RFC only reserves the name, with no provision that it exist in DNS, much less resolve to an IP that points to a real live server!)

3) It's confusing: It adds no useful information while potentially confusing readers (e.g., is this IP reserved as a part of the RFC? is this IP permanently linked to the domain and thus can be hard-coded?). At worst, it can lead uninformed users to start using the IP in lieu of the domain, which is just plain wrong.

4) This is information that can be very easily looked up.

Code65536 (talk) 05:50, 6 April 2009 (UTC)

Source for "example.edu"?[edit]

It says "while it was reserved for the edu domain by the Internet Corporation for Assigned Names and Numbers (ICANN) since 2000", but there is no source linked/mentioned. --80.130.161.44 (talk) 14:08, 26 March 2012 (UTC)