Hi Carl, Le Sat, 18 Feb 2017 09:31:19 -0600 Carl Karsten <[email protected]> a écrit:
> dc10b is the dnsmasq server Ok; and I assume that you are running 'host' on another machine, right? > I am using a modified version of this: > https://anonscm.debian.org/git/debconf-video/ansible.git/tree/roles/dhcp-server Can't say it tells me much. :) > I haven't checked in the mods yet because things are still a little > wonky. git diff ... skimmed, don't see anything that would affect > dnsmasq. > > juser@dc10b:~$ cat /etc/dnsmasq.d/local.conf > ## Ansible managed > > interface=eth-local > domain=lca2017.lan > dhcp-range=10.20.1.10,10.20.1.254,6h > dhcp-option-force=210,/srv/tftp/ > dhcp-boot=pxelinux.0 > dhcp-authoritative > enable-tftp > tftp-root=/srv/tftp And what's the /etc/hosts? > Hmm, on an openwtt ap running dnsmasq: > > root@tpap:~# cat /etc/resolv.conf > search lan > nameserver 127.0.0.1 > > root@tpap:~# cat /etc/hosts > 127.0.0.1 localhost > > root@tpap:~# nslookup tpap > Server: 127.0.0.1 > Address 1: 127.0.0.1 localhost > Name: tpap > Address 1: 192.168.1.2 tpap.lan What's 'tpap' supposed to be? Anyway, my guess: your dnsmasq server has its own name listed in its /etc/hosts with 127.0.1.1 as the matching IP, and your dnsmasq config does not contain option no-hosts, so your dnsmasq uses its /etc/hosts when resolving a name; ergo, it resolves its own name to 127.0.1.1. Amicalement, -- Albert. _______________________________________________ Dnsmasq-discuss mailing list [email protected] http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss
