5 ms·

For me DNS lookup fails (using dig, dns-sd, dscacheutil). Maybe an ISP thing? Edit: Ah, I see (quoted in the shortest URLs page): > Dotless domains will not b

For me DNS lookup fails (using dig, dns-sd, dscacheutil). Maybe an ISP thing? Edit: Ah, I see (quoted in the shortest URLs page): > Dotless domains will not be universally reachable and the SSAC recommends strongly against their use. As a result, the SSAC also recommends that the use of DNS resource records such as A, AAAA, and MX in the apex of a TopLevel Domain (TLD) be contractually prohibited where appropriate and strongly discouraged in all cases. https://www.icann.org/en/announcements/details/new-gtld-dotless-domain-names-prohibited-30-8-2013-en https://www.icann.org/en/announcements/details/new-gtld-dotl... BTW, http://ai./ http://ai./ doesn't work for me neither.

hug 4y ago
Not ISP-dependent, but DNS-server dependent. The recommendation is also just that: It's not enforced. The TLD can decide to serve those records at the apex if it wishes, and any given DNS server should look them up as requested. It just so happens in your case it doesn't -- Windows DNS, for example, will not serve the TLD's A record. Regardless, in your case, `dig pn. +noall +comments`, you'll likely see SERVFAIL. Trying `dig pn. +noall +comments @8.8.8.8` and you'll see that you get a status of NOERROR. (And, of course, `dig pn. +short @8.8.8.8` will give you the correct IP of 139.162.17.173)
- masswerk 4y ago
  ISP related in so far as this is where most people get their DNS queries resolved by default (DNS servers configured with DHCP).