[Dnsmasq-discuss] DNSmasq forwarding to DNS doesn't works
Matthias Andree
matthias.andree at gmx.de
Fri Aug 26 16:29:53 BST 2011
Am 26.08.2011 17:15, schrieb Jérémie SYLVAND:
> Hello
>
> Thank you for your answers.
>
> I have tried what you told me, in different thing :
> using resolv.conf with only 127.0.0.1
> with 127.0.0.1 and one of my ISP nameserver
>
> Not using resolv.conf by the line no-resolve in the dnsmasq.conf :
> with and without this line : server=127.0.0.1
> and with all my ISP nameserver addresses
> server=89.2.0.1
> server=89.2.0.2
> server=212.30.96.123
> server=213.203.124.147
> in the dnsmasq.conf
>
> And it still doesn't works
>
> My logs :
>
> # tail -f /var/log/messages
> Aug 26 16:55:23 fedoraserver abrtd: Corrupted or bad crash
> /var/spool/abrt/ccpp-1314370523-6770 (res:2), deleting
> Aug 26 16:58:02 fedoraserver dnsmasq[7256]: exiting on receipt of SIGTERM
> Aug 26 16:58:02 fedoraserver dnsmasq[7293]: started, version 2.52
> cachesize 6000
> Aug 26 16:58:02 fedoraserver dnsmasq[7293]: compile time options: IPv6
> GNU-getopt DBus no-I18N DHCP TFTP
> Aug 26 16:58:02 fedoraserver dnsmasq-dhcp[7293]: DHCP, IP range
> 192.168.0.180 -- 192.168.0.200, lease time 12h
> Aug 26 16:58:02 fedoraserver dnsmasq[7293]: using nameserver
> 213.203.124.147#53
> Aug 26 16:58:02 fedoraserver dnsmasq[7293]: using nameserver
> 212.30.96.123#53
> Aug 26 16:58:02 fedoraserver dnsmasq[7293]: using nameserver 89.2.0.2#53
> Aug 26 16:58:02 fedoraserver dnsmasq[7293]: using nameserver 89.2.0.1#53
> Aug 26 16:58:02 fedoraserver dnsmasq[7293]: read /etc/hosts - 3 addresses
OK, so the nameserver configuration works, but it has not logged any
queries that it would have forwarded so far - check if there are any
further down.
Please check:
- if bind-interfaces makes any difference
- possibly remove the interface configuration tying dnsmasq to eth0 just
to see if it helps
- your resolv.conf on the fedoraserver should point to the primary eth0
address
- Firewall configuration
- /etc/resolv.conf and /etc/host.conf on the clients
- possibly use wireshark or tcpdump to check port 53 traffic (possibly
check various interfaces)
More information about the Dnsmasq-discuss
mailing list