on startup dnsmasq show this
Jun 17 14:43:29 alix2c3 daemon.info dnsmasq[8125]: compile time options: IPv6 GNU-getopt ISC-leasefile no-DBus no-I18N TFTP
>> Jun 17 14:43:29 alix2c3 daemon.warn dnsmasq[8125]: warning: setting capabilities failed: Operation not permitted
Jun 17 14:43:29 alix2c3 daemon.warn dnsmasq[8125]: running as root
Jun 17 14:43:29 alix2c3 daemon.info dnsmasq[8125]: using nameserver 192.168.62.4#53 for domain gf.local
Jun 17 14:43:29 alix2c3 daemon.info dnsmasq[8125]: using nameserver 192.168.62.4#53 for domain hoerst.net
Jun 17 14:43:29 alix2c3 daemon.info dnsmasq[8125]: reading /tmp/dhcp.leases
Jun 17 14:43:29 alix2c3 daemon.info dnsmasq[8125]: reading /tmp/resolv.conf.auto
etc.
dnsmasq now should resolve those 2 domains on specified NS.. but on Kamikaze device
Server:    127.0.0.1
Address 1: 127.0.0.1 localhost.
nslookup: can't resolve 'capricorn.gf.local': Name or service not known

detailled:
nslookup capricorn.hoerst.net 192.168.62.4
Server:    192.168.62.4
Address 1: 192.168.62.4
nslookup: can't resolve 'capricorn.hoerst.net': Name or service not known

on 192.168.62.4:
nslookup capricorn.hoerst.net 192.168.62.4
Server:         192.168.62.4
Address:        192.168.62.4#53
Name:   capricorn.hoerst.net
Address: 10.11.12.13

There is no firewall between

ciao gerd

No, it seems dnsmasq wants to answer these zones on an interface of its own with the IP 192.168.62.4. You need to make it forward the requests to 192.168.62.4.

Hi !

this was done by the local option
un 17 14:43:29 alix2c3 daemon.info dnsmasq[8125]: using nameserver 192.168.62.4#53 for domain gf.local
Jun 17 14:43:29 alix2c3 daemon.info dnsmasq[8125]: using nameserver 192.168.62.4#53 for domain hoerst.net
this means requests for thes domains will be forwarded to the nameserver, but an explicit request with nslookup hooks up (NX domain)
on all other machines in the net a nslookup hostename 192.168.62.4 works like charm.
I also remeber that before i "upgraded" kaimaze to kernel .6 it worked.
I saved the uci settings from old installation and setup same way new one...
but i hve no idea from which option this comes:

Jun 17 14:43:29 alix2c3 daemon.warn dnsmasq[8125]: warning: setting capabilities failed: Operation not permitted

This wasn't in previous installation.

ciao gerd

Sorry, you're right. Your config should work. What version of kamikaze are you using?
Capability not there should be no problem:
http://osdir.com/ml/network.dns.dnsmasq … 00020.html

This doesn't make sense actually, because nslookup is asking 192.168.62.4 directly, and it gets no answer. Maybe 192.168.62.4 isn't configured right.

i'm using svn few days ago...

btw: this is on a machine in the net
nslookup capricorn.hoerst.net 192.168.62.4
Server:         192.168.62.4
Address:        192.168.62.4#53

Name:   capricorn.hoerst.net
Address: 10.11.12.13

and this from another ap (wrt54g)
root@ap57:~# nslookup capricorn.hoerst.net 192.168.62.4
Server:     capricorn.gf.local
Address:    192.168.62.4
Name:       capricorn.hoerst.net
Address:    10.11.12.13

So dns is running correct...
queries are allowed from local net (10.11.12.0 and 192.168.62.0) kamikaze box has 192.168.62.254...

ciao gerd

(Last edited by gerd on 18 Jun 2008, 13:05)

Use tcpdump (filtered for port 53) to see if the lookup from "nslookup capricorn.hoerst.net 192.168.62.4" actually leaves the router towards the server.