4 ms·
Glad to see that http://pn/ http://pn/ and http://pn./ http://pn./ are both apparently working. I'm pretty sure that at one point I had to supply the trailing
by ttctciyf 7y ago
Glad to see that http://pn/ http://pn/ and http://pn./ http://pn./ are both apparently working.
I'm pretty sure that at one point I had to supply the trailing dot to make the browser (or resolver) believe it was a real hostname.
- donatj 7y agoWhat is the deal with that?
- ch_sm 7y agoYeah, how does that work?
- 3pt14159 7y agoI'd guess it's the TLD of the Pitcairn Islands set to resolve to this random page. For example http://ca. resolves to the Canadian domain registrar.
- colejohnson66 7y agoNot necessarily a random page, but an “it works” page so you know your server works.
- lioeters 7y agoHow perplexing that it works at all! I want to know how that works.
- colejohnson66 7y agoIt’s just a TLD that actually resolves; Most don’t. For example, http://com./ http://com./ doesn’t resolve even though it has “subdomains”. This does though beg the question: can a second level domain (root website) have (what we call) subdomains and not resolve itself? For example, example.example.com would resolve, but example.com wouldn’t?
- BenjiWiebe 7y agoShould be easy to set up, especially if you have your own authoritative DNS server. Just don't publish an A record for your main domain.
- lioeters 7y agoThanks for the clarification. I see, so an owner can choose to resolve the top-level domain by itself, I didn't know that. When I visit "com.", indeed it doesn't resolve and the browser falls back to "www.com" (which exists). That makes me wonder, if I wanted a TLD by itself to resolve to my own site, is it even feasible for a "regular person"? What's served on "http://pn/" http://pn/" looks like someone's experiment, but I guess they must own the TLD (or have connections to the owner)..?
- naniwaduni 7y agoYes, this is quite common.
- anchpop 7y agohttp://ai./ http://ai./ works as well. It's too bad neither has HTTPS set up
- baddox 7y agoWhen I click on the first link in iOS Safari I get sent to a search results page served by my (read: my parents’) ISP. That’s pretty disturbing. The second link appears to work. It’s a page that says “It works!” but it’s not HTTPS so of course I have no way of knowing whether that’s the ISP playing tricks as well. ;)
- lostgame 7y agoTime to change ISP's or check for malware :/
- oplav 7y agoWhy is that disturbing? For me, the name doesn't resolve (http://pn/ http://pn/). Assuming you are using your parents' ISP's default DNS servers, isn't it a safe, though less-than-desirable, result for the ISP to forward you to a search page when resolution fails?
- barsonme 7y agoNo, the DNS should return NXDOMAIN and that’s it.
- BenjiWiebe 7y agoUsing a different DNS server not provided by the ISP would most likely solve the problem. You can do so in either the router or your computer/phone. Two well known and performant public DNS servers are found at 1.1.1.1 (CloudFlare) and 8.8.8.8 (Google).