[Dnsmasq-discuss] v2.26 on SuSE 8.1 almost working! (I think)...
Simon Kelley
simon at thekelleys.org.uk
Mon Mar 13 08:23:36 GMT 2006
David Mirly wrote:
> ...but something is a bit off (no pun intended).
>
> I compiled the source on a i386 (Pentium 200 mhz) running SuSE 8.1 [I
> know, I need to upgrade].
> compiling seemed to go fine with no errors that I saw.
>
> The system is multihomed with eth0 connected to the cable modem and
> getting it's IP via DHCP from the ISP.
> eth1 is connected to my household lan (192.168.1.10 is it's address and
> the machines at my house are
> 192.168.1.x).
>
> Pretty standard stuff and exactly what dnsmasq seems to be intended for.
>
> dnsmasq seems to start fine but here is it's output when I attempt to
> access seti.org from dig from a client machine that
> I changed the DNS IP to 192.168.1.10. The name servers it is finding
> in resolv.conf are good. If I dig to either of them
> directly then the query works fine. I am not using a dnsmasq.conf file.
>
> (there are some IPv6 addressed in the /etc/hosts that is complaining
> about - I'm not worried about those)
>
>
> Mar 12 23:07:02 linux dnsmasq: started, version 2.26 cachesize 150
> Mar 12 23:07:02 linux dnsmasq: compile time options: no-IPv6 GNU- getopt
> RTNetlin
> k ISC-leasefile no-DBus no-I18N
> Mar 12 23:07:02 linux dnsmasq: bad address at /etc/hosts line 15
> Mar 12 23:07:02 linux dnsmasq: bad address at /etc/hosts line 17
> Mar 12 23:07:02 linux dnsmasq: bad address at /etc/hosts line 19
> Mar 12 23:07:02 linux dnsmasq: bad address at /etc/hosts line 20
> Mar 12 23:07:02 linux dnsmasq: bad address at /etc/hosts line 21
> Mar 12 23:07:02 linux dnsmasq: bad address at /etc/hosts line 22
> Mar 12 23:07:02 linux dnsmasq: read /etc/hosts - 3 addresses
> Mar 12 23:07:02 linux dnsmasq: reading /etc/resolv.conf
> Mar 12 23:07:02 linux dnsmasq: using nameserver 204.127.202.19#53
> Mar 12 23:07:02 linux dnsmasq: using nameserver 216.148.227.79#53
> Mar 12 23:07:28 linux dnsmasq: query[A] 204.127.198.4 from 192.168.1.151
> Mar 12 23:07:28 linux dnsmasq: config 204.127.198.4 is 204.127.198.4
> Mar 12 23:07:28 linux dnsmasq: query[A] seti.org from 192.168.1.151
> Mar 12 23:07:28 linux dnsmasq: forwarded seti.org to 216.148.227.79
> Mar 12 23:07:28 linux dnsmasq: forwarded seti.org to 204.127.202.19
> Mar 12 23:07:33 linux dnsmasq: query[A] seti.org from 192.168.1.151
> Mar 12 23:07:33 linux dnsmasq: forwarded seti.org to 216.148.227.79
> Mar 12 23:07:33 linux dnsmasq: forwarded seti.org to 204.127.202.19
>
>
> I couldn't see how to get any further output to help with
> troubleshooting but will certainly follow any guidance you want to give.
>
The configuration is so simple that it can't really be wrong: My guess
is that some firewall rule is blocking packets. Do you have iptables in
use? what ruleset?
Cheers,
Simon.
More information about the Dnsmasq-discuss
mailing list