aaa.aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa.com
211–220 of 313 posts
Earlier quoted context omitted.
That's very weird! How did you even find this?
Sometimes instead of typing google.com I end up typing gooooooooogle.com
Speaking of sketchy websites :)
Would have been cool though if someone at google had bought all gooo... domains.
TAC* is the best compression format available for the web today! By using revolutionary scientific methods, research teams at RSG and the Beige Programming ensemble were able to a compose a complex software tool that expels many of the myths that surround modern file compression techniques. The secret of TAC compression is not that it makes files smaller, but that it makes files bigger, much bigger.* This provides the end user with a compression tool to meet almost any need in today's bandwidth and gig overloaded computing world.
Love it. This is going in the toolbox along with http://shadyurl.com
Earlier quoted context omitted.
Huh, this is weird! The DNS record is no longer in the root zone itself (I think it used to be?) and some recursive resolvers seem to filter out the bare-TLD query or response. But the A record still exists inside the ai zone... so I'm not sure who is right, so to speak!
The A record was never in the root zone. The root zone has an NS record for ai TLD which delegates authority to ai nameservers. You can try `dig @a.root-servers.net ai NS` to get the nameserver `a.lactld.org.` which is authoritative for ai. You can now try `dig @a.lactld.org ai A` to get it (that's how recursive resolves generally work)
By the way:
> The A record was never in the root zone.
Are you sure of that? I don't have any proof, but my impression was that the DNS registry for ai (which was also just Vince Cate...) was able to ask for it because at one time the root zone was less restrictive in what RRtypes could be placed there for TLDs. But that might just be repeating someone else's mistaken impression.
OK, I went and looked in the Internet Archive
https://web.archive.org/web/20090716164810/http://www.intern...
and this version of the root zone from 2009 does indeed not have an A record for ai, just ordinary NS delegations. So it seems like your explanation is confirmed, and there must be a change in some recursive resolver behavior. (I tried from four different Linux systems on different networks and all refused to resolve it, so there really must be something that's changed more widely, not just my home router.)
Earlier quoted context omitted.
Below is a link I generated for https://twitter.com/home http://www.5z8.info/winamp-cracked.exe_x8c5se_how2pipebomb Thank you for this, I laughed hard.
That totally reminds me of this story: http://www.5z8.info/awesome-real-life-headshots_q2h6fv_linke...
Edit: if someone need the url at work: https://m.slashdot.org/story/17042
Anyway, cool project. It's okay to build something for a laugh every now then. I know these days sometimes I forget I used to do this for fun. Have a good weekend all.
Earlier quoted context omitted.
The A record was never in the root zone. The root zone has an NS record for ai TLD which delegates authority to ai nameservers. You can try `dig @a.root-servers.net ai NS` to get the nameserver `a.lactld.org.` which is authoritative for ai. You can now try `dig @a.lactld.org ai A` to get it (that's how recursive resolves generally work)
Yeah, so I think I'm seeing something weird where some software isn't allowing this particular recursive query? I'll dig into it more. By the way: > The A record was never in the root zone. Are you sure of that? I don't have any proof, but my impression was that the DNS registry for ai (which was also just Vince Cate...) was able to ask for it because at one time the root zone was less restrictive in what RRtypes cou…
Earlier quoted context omitted.
I've worked in such places. The reason it is that way is because you will receive a broken description/specification/story of what you are supposed to implement. You have a choice to make when that happens, you either implement it as specified or you reject it because it is broken. The problem is that if you do reject it then it will take about 6 months to get back a specification that is broken in another way and th…
Enterprise developer here. Exactly this. If you reject the spec, you won't get another one before the deadline that was committed before you got the spec you want to reject.
Back in the early days of web hosting I recall that a customer had a domain name that was literally as long as ICANN would allow at the time. It was very nearly a full sentence. I don't recall the limit but this domain aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa.com is 57 characters (not including .com) and I think that sounds familiar. One could have a lot of fun with that if they wanted to (and such as…
Interesting where is frontier who can make most long 256+ url shorters & lengther vector hahah
like tiny.cc -> aaaaaaaa...aaa -> goog.gl -> bbb...bb -> etc