[Dnsmasq-discuss] DNSmasq forwarding to DNS doesn't works

Frederick C. Damen fred at damen.org
Fri Aug 26 17:10:41 BST 2011


from the fedoraserver machine try
ping 89.2.0.1
traceroute 89.2.0.1
telnet 89.2.0.1 53
this should tell you if you at least have conectivity;
repeat with each upstream dns server IP address.

If your (r)syslog log level is set higher than the log-queries then they 
will not make it to the (r)syslog file.  Try using the 
--log-facility=/tmp/dnsmasq-queries
Then try ping google.com

Do not put the IP address of you ethx IP addresses in /etc/resolv.conf. 
  Every machine can refer to its self as 127.0.0.1.  dnsmasq is smart 
enough to ignore this address and not use it as an upstream dns server. 
  I have not seen anything stating that dnsmasq will ignore the ethx IP 
address as a upstream dns server.  Besides 127.0.0.1 address should 
always work on the local machine even if your networking is all screwed up.

Fred

On 08/26/2011 10:29 AM, Matthias Andree wrote:
> 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)
>
> _______________________________________________
> Dnsmasq-discuss mailing list
> Dnsmasq-discuss at lists.thekelleys.org.uk
> http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss



More information about the Dnsmasq-discuss mailing list