[Dnsmasq-discuss] I've lost my ability to resolve local machine names without a domain suffix

Chris Green cl at isbd.net
Sun Oct 20 12:25:31 BST 2019


On Sun, Oct 20, 2019 at 12:17:50PM +0200, john doe wrote:
> On 10/20/2019 10:15 AM, Chris Green wrote:
> > On Sun, Oct 20, 2019 at 08:59:03AM +0200, Geert Stappers wrote:
> >> On Sat, Oct 19, 2019 at 10:21:26PM +0100, Chris Green wrote:
> > I don't add any command line options to dnsmasq, my changes to the
> > defaults in /etc/dnsmasq.conf are as follows:-
> >
> >     domain-needed
> >     bogus-priv
> >     expand-hosts
> >     domain=zbmc.eu
> >     dhcp-range=192.168.1.80,192.168.1.127,12h
> >     dhcp-option=3,192.168.1.1
> >     dhcp-authoritative
> >     local=/zbmc.eu/
> >     cname=bbb,beaglebone
> >     cname=mx201,maxine-X201
> >     cname=ben,DESKTOP-978VD5M
> >     cname=oki,MC342-AE529C
> >     dhcp-host=00:BB:3A:E9:A3:15,maxineKindle
> >     dhcp-host=00:09:B0:C9:CE:81,onkyoTx-nr616
> >     dhcp-host=28:EF:01:2D:EB:07,chrisKindle
> >     dhcp-host=08:EB:74:9D:47:53,humaxFreeview
> >     dhcp-host=2C:08:8C:CC:9A:9E,humaxYouview
> >     dhcp-host=00:1F:E2:4E:8F:CA,maxineStudy
> >     dhcp-host=AC:AE:19:2C:3F:5A,roku
> >     dhcp-host=10:FE:ED:63:29:74,TL-WA7210
> >     dhcp-host=00:25:36:AE:52:9C,192.168.1.50
> >
> > So I have a domain= like you.
> >
> >> What happens at _client_ side, actually happens at _client_ side.
> >>
> > Yes, of course, and it seems to be all OK now after restarting
> > everything (but no other changes) so *something* had got out of kilter
> > so that unqualified names weren't working but was fixed by the reboots.
> > It may well be that upgrades (that don't usually require restarts on
> > Linux) had got some systemd bits in a tangle which a restart sorted out.
> >
> >>
> >>> ... and why doesn't a local name only work on the machine running dnsmasq?
> >>
> >> Sorry, can't parse that question. If the question was
> >> } ... and why does a local name only work on the machine running dnsmasq?
> >> or
> >>> ... and why doesn't a local name work on the machine running dnsmasq?
> >> say so.  Yes, do put effort in asking a question.[1]
> >>
> > Asking for the address of an unqualified name on the machine running
> > dnsmasq fails:-
> >
> >     chris at newdns$ host esprimo
> >     Host esprimo not found: 3(NXDOMAIN)
> >     chris at newdns$ host esprimo.zbmc.eu
> >     esprimo.zbmc.eu has address 192.168.1.3
> >     chris at newdns$
> >
> > Is there any way to fix this?  It's not incredibly impoprtant because
> > I only rarely do anything (as in log in and run programs) on that
> > machine but it would be nice if it worked the same as the other
> > machines on the LAN.
> >
> > It's presumably down to the order in which it runs its client DHCP
> > requests versus when dnsmasq starts so that it can answer itself.
> >
> 
> You are not using 'dhcp-fqdn' (1)?
> 
> 1)  http://www.thekelleys.org.uk/dnsmasq/docs/dnsmasq-man.html
> 
No, and reading what it does I can't see any good reason for doing so.
My LAN runs on a single subnet so all systems *must* have unique names
anyway.

-- 
Chris Green



More information about the Dnsmasq-discuss mailing list