1- Periods (.) don't do anything after a domain (ie www.weebly.com.), but they are useful for preventing the browsers from redirecting to http://www.to.com/
2- The real domain we're looking at: "to" -- no "suffix" attached (TLD: top-level domain)
3- The .to registry added an A-record for the "to" domain, which resolves correctly.
Actually the period at the end is part of the DNS standard, without it, your machine's search path is searched first (e.g. in resolv.conf on Unix/Linux)
So if your ISP is AOL, you might have a search path of aol.com
so looking up "to" will first try to.aol.com if that exists it will go there. Putting a "." at the end will let it go straight there.
This isn't normally a problem because it's not like aol is going to set up google.com.aol.com. But really everyone should have periods at the end of domains.
I believe the justification was so they could use unified cookies across all their properties -- they set the cookie for "com.com", and then it was available to news.com.com, search.com.com, downloads.com.com, etc., in the same way that yahoo.com cookies are available to news.yahoo.com, sports.yahoo.com, etc.
A little kid's? Don't know what you are talking about, and a quick google gives no relevant results. Perhaps old meanings die quietly over time? Also, this thread is the top google reference for "no workie" racism, doesn't look like there is much keyword competition.
2- The real domain we're looking at: "to" -- no "suffix" attached (TLD: top-level domain)
3- The .to registry added an A-record for the "to" domain, which resolves correctly.
[Edit: Looks like .cm does this too:
;; ANSWER SECTION:
cm. 86400 IN A 195.24.205.60]