3 ms·

Neither of those URLs work for me (DNS doesn't resolve).

• arthurcolle 5y ago
  use a better dns resolver
  • mastazi 5y ago
    I don't think it's a dns resolver issue. I'm intentionally using 8.8.8.8 to prove the point (same results with other mainstream services like 1.1.1.1 by the way): ----- $ nslookup google 8.8.8.8 Server: dns.google Address: 8.8.8.8 Name: google. ------ $ nslookup google. 8.8.8.8 Server: dns.google Address: 8.8.8.8 Name: google ----- (Edit: formatting).
    • zamadatix 5y ago
      It's the local client not the resolver. Try "ai."
      • deleted 5y ago
        [deleted]
      • mastazi 5y ago
        I had no issue with ai, I'm referring to google, see the nslookup outputs I pasted above.
  • BareNakedCoder 5y ago
    Or use a worse DNS resolver. Your ISP may be trying to cash in on DNS names that don't resolve / ain't found by instead sending you to another website that pays the ISP a small fee.
• zamadatix 5y ago
  https://google https://google. isn't supposed to work, for ai try http://ai./ http://ai./ instead.
  • decrypt 5y ago
    http://ai./ http://ai./ and https://ai./ https://ai./ does not work either. Is that an issue with my DNS resolver?
    • rany_ 5y ago
      If you are using systemd's resolved you will have to disable `LLMNR` and enable `ResolveUnicastSingleLabel`. It should look something like this: $ cat /etc/systemd/resolved.conf [Resolve] LLMNR=no ResolveUnicastSingleLabel=yes