On Sat, Oct 19, 2019 at 09:00:27PM +0200, Geert Stappers wrote:
> On Sat, Oct 19, 2019 at 07:31:49PM +0100, Chris Green wrote:
> > I've run dnsmasq for several years on my small home LAN.  I'm running
> > dnsmasq on a raspberry-pi and most of the client machines on the LAN
> > are linux (xubuntu).
> > 
> > I've suddenly lost the ability to resolve local machine names without
> > a domain suffix, e.g.:-
> > 
> >     On the Raspberry Pi itself:-
> > 
> >     chris@newdns$ host esprimo
> >     Host esprimo not found: 3(NXDOMAIN)
> >     chris@newdns$ host esprimo.zbmc.eu
> >     esprimo.zbmc.eu has address 192.168.1.3
> >     chris@newdns$ 
> > 
> > ... and on a Linux machine on the LAN:-
> > 
> >     chris$ host t470
> >     Host t470 not found: 2(SERVFAIL)
> >     chris$ host t470.zbmc.eu
> >     t470.zbmc.eu has address 192.168.1.92
> >     chris$ 
> > 
> > 
> > So what's gone wrong/changed?  The raspberry pi is pretty up to date:-
> > 
> >     chris@newdns$ uname -a
> >     Linux newdns 4.19.66-v7+ #1253 SMP Thu Aug 15 11:49:46 BST 2019 armv7l 
> > GNU/Linux
> >     chris@newdns$ more /etc/issue
> >     Raspbian GNU/Linux 9 \n \l
> >     chris@newdns$ dnsmasq --version
> >     Dnsmasq version 2.76  Copyright (c) 2000-2016 Simon Kelley
> > Compile time options: IPv6 GNU-getopt DBus i18n IDN DHCP DHCPv6 no-Lua 
> TFTP conntrack ipset auth DNSSEC loop-detect inotify 
> > 
> >     This software comes with ABSOLUTELY NO WARRANTY.
> >     Dnsmasq is free software, and you are welcome to redistribute it
> >     under the terms of the GNU General Public License, version 2 or 3.
> >     chris@newdns$ 
> > 
> > I don't *think* I've changed anything in /etc/dnsmasq.conf recently.
> > 
> > Help!! :-)
> 
> On a Linux system
>   grep -e search -e domain /etc/resolv.conf
> 
    chris$ grep -e search -e domain /etc/resolv.conf
    search zbmc.eu
    search zbmc.eu
    chris$ 

Is that what you were asking me to do?

Strangely I seem to be able to resolve local names without a suffix
now.  I have rebooted a few machines, maybe something simply got
full/misconfigured and a reboot has cleared it up.  Or, more likely I
suspect, systemd reconfigured something during system updates and the
reboot was needed to get things properly sorted.

-- 
Chris Green

_______________________________________________
Dnsmasq-discuss mailing list
Dnsmasq-discuss@lists.thekelleys.org.uk
http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss

Reply via email to