richardvo...@gmail.com on 26/01/10 14:23, wrote:
On Tue, Jan 26, 2010 at 3:19 AM, Adam Hardy <adam....@cyberspaceroad.com> wrote:
richardvo...@gmail.com on 26/01/10 01:56, wrote:
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

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@isengard:~$ cat /etc/resolv.conf
domain isengard.localdomain
search isengard.localdomain
nameserver 127.0.0.1
nameserver 194.74.65.68

Perhaps your resolv.conf is causing requests for
client.isengard.localdomain while dnsmasq made an entry for
client.localdomain

Here's a query log:

Jan 26 14:49:13 localhost dnsmasq[31068]: reading /etc/resolv.conf
Jan 26 14:49:13 localhost dnsmasq[31068]: using nameserver 194.74.65.68#53
Jan 26 14:49:13 localhost dnsmasq[31068]: ignoring nameserver 127.0.0.1 - local
interface
Jan 26 14:49:13 localhost dnsmasq[31068]: using local addresses only for domain
localdomain
Jan 26 14:49:13 localhost dnsmasq[31068]: query[A] MFD8FDC7.isengard.localdomain
from 127.0.0.1
Jan 26 14:49:13 localhost dnsmasq[31068]: config MFD8FDC7.isengard.localdomain
is NXDOMAIN-IPv4

So it's exactly what you predicted - but I've read thro the whole config and
can't see what I need to change. Here's my dnsmasq.conf again:

domain-needed
bogus-priv
filterwin2k
server=/localdomain/127.0.0.1
local=/localdomain/
expand-hosts
domain=localdomain
dhcp-range=192.168.0.3,192.168.0.254
dhcp-option=option:router,192.168.0.2
dhcp-option=option:mtu,1500

I think that resolv.conf is wrong - should domain=localdomain and not
isengard.localdomain?

resolv.conf is being constantly rewritten by dhclient3 which is doing obtaining
an ip address via dhcp for the external NIC. I can see now that I had

supersede domain-name "isengard.localdomain"

in the dhclient3.conf - doh! So that was it.

Thanks for your help,
regards
Adam


Reply via email to