Ernillew / wl500g

Automatically exported from code.google.com/p/wl500g
0 stars 0 forks source link

dnsmasq not listening on loopback #244

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. try to do a DNS lookup using localhost as DNS-server (e.g. using dig 
@127.0.0.1 domain) on the router

What is the expected output? What do you see instead?
dnsmasq should answer like it does if I start dig on another host (e.g. on my 
ps using dig @router-ip domain)
Instead, it fails after a timeout
Using the LAN-IP of the Router (192.168.1.1) instead of loopback IP won't work 
either!

What version of the product are you using?
WL500W-1.9.2.7-rtn-r3121

Please provide any additional information below.
I want to use a special config, where dnsmasq uses /opt/etc/resolv.conf and 
querys all servers paralell and then just have "nameserver localhost" in 
/etc/resolv.conf
This setup worked with the -d version firmware.
I read the dnsmasq manpage, and it says dnsmasq should always listen on the 
loopback interface, if not explicitly disabled

Original issue reported on code.google.com by josef.schneider on 7 Jul 2011 at 9:26

GoogleCodeExporter commented 9 years ago
Nothing changed in dnsmasq between -d & -rtn branches. As usual, use 
/usr/local/etc/dnsmasq.conf to add custom parameters to dnsmasq and for total 
replace of config you have to restart dnsmasq. And we don't perform any special 
steps to disable listen on loopback, you cat check it by "cat /etc/dnsmasq.conf"

/etc/resolv.conf created by "rc" at boot. 

Original comment by lly.dev on 8 Jul 2011 at 6:26

GoogleCodeExporter commented 9 years ago
Default config:

$ netstat -aun|grep 53
udp        0      0 0.0.0.0:53              0.0.0.0:*
udp        0      0 :::53                   :::*
$ grep interface /etc/dnsmasq.conf
interface=br0
$

Original comment by lly.dev on 9 Jul 2011 at 11:18

GoogleCodeExporter commented 9 years ago
Confirmed, will take a look.
Either disable ipv6 (if not used) or use dig @::1 by now

Original comment by themiron.ru on 9 Jul 2011 at 8:45

GoogleCodeExporter commented 9 years ago
"nameserver ::1" in /etc/resolv.conf works! Thanks!

Original comment by josef.schneider on 9 Jul 2011 at 9:01

GoogleCodeExporter commented 9 years ago
fixed with r3143

Original comment by themiron.ru on 11 Jul 2011 at 7:01