dnsmasq.to.pee...@spamgourmet.com on 26/01/10 08:20, wrote:
On Mon, Jan 25, 2010 at 12:20 PM, Adam Hardy
<adam....@cyberspaceroad.com> wrote:
[leases work but]
There must be something missing from my dnsmasq config because I see now
that
any attempt to use the host names of dhcp clients from the gateway
server fail
with " unknown host ...". I'm on debian stable if that makes any
difference
Richard wrote:
Sounds like your gateway is not using dnsmasq for lookups. dnsmasq
tells dhcp clients to use its services, but the gateway you will have
to manually configure in /etc/resolv.conf to send requests to the
local dnsmasq process.
Adam wrote:
I've got 127.0.0.1 in my /etc/hosts
Richard's zeroed in on the problem I reckon.
Here's the Debian Way <tm> to fix it, imho.
Did you apt-get install resolvconf? In debian that takes care of the
dnsmasq usage.
And you can add
dns-nameservers 8.8.8.8 4.2.2.4
to your interfaces file for the interface connecting to the internet on
the router for when dnsmasq doesn't have it in cache. (Use:
dns-nameservers 192.168.0.2 8.8.8.8 4.2.2.4 for the lan setting).
When you've done that, apt-get install dnsutils and see what dig
google.com or such on the router tells you is the IP of the nameserver you
are using. It should be 127.0.0.1.
Hi PJ
sounds interesting - but the external interface gets has a DHCP ip address so I
can't put that into /etc/networking/interfaces. Or are you talking just
temporarily for debugging purposes?
