[Dnsmasq-discuss] dnsmasq replies with 127.0.01
cquike at arcor.de
Mon Aug 24 22:40:01 BST 2009
yes, that right, the hostname is assigned to 127.0.0.1 via the /etc/hosts.
Since the server gets its IP using DHCP, I could not hardcode the IP
in /etc/hosts. However, the master DNS resolves my hostname properly, so that
solved the problem.
At home, however, where I have another setup, my ISP doesn't resolve my
hostname, of course. That forces me to put my hostname in /etc/hosts bound to
127.0.0.1, so the problem persists... Anyway, in my home setup it is not so
El Domingo, 23 de Agosto de 2009, Carlos Carvalho escribió:
> Enrique (cquike at arcor.de) wrote on 22 August 2009 23:51:
> > I am using dnsmasq in the context of the virt-manager software. My
> > server contains the virtualization software, including dnsmasq. I have
> > an issue when client of dnsmasq (one of the virtual machines) tries to
> > resolve the name of the server. Because dnsmasq runs in the server and
> > it reads the /etc/hosts file, it returns 127.0.0.1 as the IP of the
> > server, instead of the IP associated to eth0.
> How does dnsmasq discover that name-of-the-server is 127.0.0.1? In the
> machines I run dnsmasq it's not able to guess that much. The only way
> I can imagine is that you put this entry in /etc/hosts. If so, don't.
> The only entry pointing to 127.0.0.1 should be localhost. Just put
> IP-of-the-server name-of-the-server; no need to worry about routing,
> the kernel is smart enough to discover it's local and send it to the
> internal IP.
> Dnsmasq-discuss mailing list
> Dnsmasq-discuss at lists.thekelleys.org.uk
More information about the Dnsmasq-discuss