[Dnsmasq-discuss] Non-FQD request works from older systems but not from newer ones

[Chris Green]

I have a small home network with dnsmasq running on a Raspberry Pi, it
was all working nicely with several systems running xubuntu using the
Pi DNS successfully.

I have just added a new laptop running xubuntu 17.04 and on that
system unqualified local domain name requests fail.

I.e. on an xubuntu 16.04 system:-

	chris at backup:~$ host esprimo
	esprimo.zbmc.eu has address 192.168.1.3
	chris at backup:~$ host esprimo.zbmc.eu
	esprimo.zbmc.eu has address 192.168.1.3
	chris at backup:~$ host pi
	pi.zbmc.eu has address 192.168.1.2
	chris at backup:~$ 

... but on the new 17.04 system:-

	chris$ host esprimo
	Host esprimo not found: 2(SERVFAIL)
	chris$ host esprimo.zbmc.eu
	esprimo.zbmc.eu has address 192.168.1.3
	chris$ host pi
	Host pi not found: 2(SERVFAIL)
	chris$ 


The only significant difference (DNS wise) that I can see between the
systems is that the 16.04 systems run the 'run by NetworkManager'
local dnsmasq whereas the new 17.04 system has its local DNS handled
by some part of systemd.  On the 17.04 system /etc/resolv.conf is:-

	chris$ more /etc/resolv.conf
	# 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
	chris$ 

... and "systemd-resolve --status" returns:-

	chris$ systemd-resolve --status
	Global
		  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/IPv4 LLMNR/IPv6
	       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

Can anyone suggest what the problem might be? (... and a fix!)

-- 
Chris Green