How to get the systemd resolver to resolve local (i.e. unqalified) names?

[Chris Green]

On Sat, Jun 03, 2017 at 05:11:59PM -0300, Kleber Leal wrote:
>    Do you have the *search* option defined with your /etc/resolv.conf?
>    nameserver x.x.x.x
>    nameserver x.x.x.y
>    search [1]zbmc.eu


Oh for heavens sake!!!!!

/etc/resolv.conf hasn't been an editable configuration file since
somewhere around 10.04.

/etc/resolv.conf in 17.04 is:-

    # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
    #     DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
    # 127.0.0.53 is the systemd-resolved stub resolver.
    # run "systemd-resolve --status" to see details about the actual nameservers.

    nameserver 127.0.0.53

As I said in my original pasting the result of "systemd-resolve --status"
is:-

    chris$ systemd-resolve --status
    Global
              DNS Domain: zbmc.eu
                          fred.com
                          bert.com
                          this.that.tv
              DNSSEC NTA: 10.in-addr.arpa
                          16.172.in-addr.arpa
                          168.192.in-addr.arpa
                          17.172.in-addr.arpa
                          18.172.in-addr.arpa
                          19.172.in-addr.arpa
                          20.172.in-addr.arpa
                          21.172.in-addr.arpa
                          22.172.in-addr.arpa
                          23.172.in-addr.arpa
                          24.172.in-addr.arpa
                          25.172.in-addr.arpa
                          26.172.in-addr.arpa
                          27.172.in-addr.arpa
                          28.172.in-addr.arpa
                          29.172.in-addr.arpa
                          30.172.in-addr.arpa
                          31.172.in-addr.arpa
                          corp
                          d.f.ip6.arpa
                          home
                          internal
                          intranet
                          lan
                          local
                          private
                          test

    Link 3 (wlp4s0)
          Current Scopes: DNS
           LLMNR setting: yes
    MulticastDNS setting: no
          DNSSEC setting: no
        DNSSEC supported: no
             DNS Servers: 192.168.1.2
                          8.8.8.8
              DNS Domain: zbmc.eu

    Link 2 (enp0s31f6)
          Current Scopes: none
           LLMNR setting: yes
    MulticastDNS setting: no
          DNSSEC setting: no
        DNSSEC supported: no
    chris$ 

So, yes, zbmc.eu is set as the search domain.

I *think* the problem is being unable to turn off LLMNR.

-- 
Chris Green