Re: After enabling IPv6 curl github.com fails, succeeds with IPv4

Martin Husemann <[email protected]> writes:

> I think both are bugs, but there might be old configurations that depend
> on them and changing behaviour always comes with a risc.

I think we should explicitly refrain from supporting back compat for
buggy semantics.

My view is

  - If there is no domain explicitly set, don't do any searching.
  - If the domain being looked up has a . anywhere, do not use the
    domain to search.

This does mean that inside example.com, foo.bar won't resolve to
foo.bar.example.com, but it also means github.com won't resolve to
github.com.baz, which is usually bad.

We should re-assess the plan while thinking about security and the new
proliferation of TLDs and use cases.  That probably leads to:

  domain keyword is used as a domain for lookup terms with no .

  search keyword, if present, can be used as a domain suffix for lookup
  terms with a .

  no defaults put in a search term; it's only if the user explicitly
  configures it

I am likely off a bit, but the point is to illustrate a choice to
security and if someone has to fix something, that's a lesser problem.