71–80 of 208 posts
I'm getting a NXDOMAIN for `dig ai.`, but when directly doing with an upstream server (i.e. 8.8.8.8 or 1.1.1.1) it perfectly works.
I assume this is the result of the `Never forward non-FQDN A and AAAA queries` setting being checked in pi-hole (which is AFAIK the default).
At one point of time, ` http://to ` resolved to a "It works!" page [1]. I've always thought it would be cool to have a URL shortener with links such as ` https://to/library ` or something similar. Oh, how much fun running your own TLD would be... [1] https://web.archive.org/web/20150319211308/http://to/
At a previous employer, we used an internal link shortener that went like http://go/whatever . Very user friendly.
Earlier quoted context omitted.
A problem with this approach is browsers love to resolve it to http://go.com , so Disney may be getting a feed of what Googlers are interested in.
I have found Chrome more willing to resolve go/foo as a web search. As a result, the Google autocomplete suggestions for terms like "go/m" are pretty amusing
> Some have A records pointing to the root servers. I’m not sure why this is - I think it might be because no DNS has been configured in the TLD zone for these TLDs. I was also curious about this. It turns out that it's because dig interprets some TLDs as DNS record types (MD, MG, MR, MX) or DNS classes (IN and CH) of the same name! Not sure why, but when given only a type or class (without a domain name), dig actual…
Earlier quoted context omitted.
I wrote myself a Chrome extension that does this, using http://l/foo style links, and using Chrome's sync to share across devices. Works well enough but limited to desktops. Some large orgs maintain internal shorteners, like http://go links at Google.
I recall seeing go link stickers around Google's Mountain View campus in the early 2010s! That was the first time I had seen something done like that, "overriding" an entire TLD zone (not that `.go` is in use, anyway) to serve custom content. Do you happen to know how Google, or any other places, do this? I assume a custom DNS resolver being forced on clients through a network could do this, or maybe hosts files for…
Earlier quoted context omitted.
Absolutely nothing wrong with ending with a .0. I suspect you are confused by n.n.n.0/24 being a network address in a /24 network which is obviously very common. However there are way more networks of other sizes that have .0 addresses in them.
I once had my ISP (BHN) assign me a public IP that ended in .0 That turned out to be a neat experiment. I regularly hit webpages and other services that would deny my connection. I guess they considered me multicast traffic or some sort of bogon.
aka.ms is short but probably not thr shortest, but I would say it is the shortest most popular url possibly. For those who don't know, that is MS's link shortner for official URLs
Earlier quoted context omitted.
At a previous employer, we used an internal link shortener that went like http://go/whatever . Very user friendly.
Say Google without saying Google. These URLs sometimes leak into the public internet, and there's especially lots of them in AOSP and Chromium code.
It's run by a character named Vince Cate who moved to Anguilla to protest taxes or something. He was from the US and gave up his US citizenship. He talked the Anguilla government into letting him set up its internet infrastructure for them.