12 ms·
In an earlier thread I was claiming that http://ai/ http://ai/ was no longer operating, but I belatedly learned that this is because systemd's DNS resolver has
by schoen 5y ago
In an earlier thread I was claiming that http://ai/ http://ai/ was no longer operating, but I belatedly learned that this is because systemd's DNS resolver has hard-coded a refusal to look up addresses with a single label from servers outside the LAN. I misinterpreted the lack of results as implying that it had been removed upstream.
https://news.ycombinator.com/item?id=27157712 https://news.ycombinator.com/item?id=27157712
So, (1) there is another site that is as short as the one you mentioned, and (2) Linux systems that default to using systemd-resolve won't be able to see either of them!
- tomklein 5y agoInteresting. Thanks for sharing!
- IvyMike 5y agoDoes http://ai./ http://ai./ (declaring the name as fully qualified) work on those systems?
- schoen 5y agoNope! I specifically tried that in the course of researching my post for the other thread, and again now. This doesn't work either on the browser or command line, including using DNS-specific software like dig or host. I think I found a spot in the systemd source code where it specifically says it will refuse to attempt single-label lookups to remote nameservers, and all my Linux systems are relying on systemd-resolve for all of their DNS lookups. If I specifically change my nameserver away from 127.0.0.53 for a query and point it anywhere else, these single-label names immediately resolve correctly again. I was also speculating in the other thread that it might be hard to get systemd to reverse this decision just for the one host "ai". Even though we now have twice as many examples of hosts that are broken by this, I still think it might be hard to get it fixed!
- jolmg 5y agoI also couldn't see ai, but my nameserver was set to my wifi router. I guess either my wifi router is using systemd-resolve or this practice isn't just done by systemd.