[Dnsmasq-discuss] 2.53rc2
clemens fischer
ino-news at spotteswoode.dnsalias.org
Tue May 25 15:14:25 BST 2010
Simon Kelley wrote:
> 2.53rc2 is now at
>
> http://www.thekelleys.org.uk/dnsmasq/release-candidates/dnsmasq-2.53rc2.tar.gz
>
> This fixes one problem (dhcp-generate-names complains if provided with
> an argument) It also updates some translations and fixes various typos
> revealed by them.
This particulra error is gone, but I cannot really verify the rest.
I let dnsmasq forward dns queries to bind-9, which worked fine
yesterday. Today I get log lines like:
dnsmasq: failed to create listening socket: Address already in use
and
dnsmasq: failed to bind server socket for : Address family not
supported by protocol
Very unfortunately, this latter error happens even with setting bind-9
off, eg. when nothing is in the way, no other dhcp or dns server.
The problem lies with dnsmasq binding the wildcard addresses. Not even
the setting:
except-interface=nic0
except-interface=nicI
except-interface=lo
no-dhcp-interface=nic0
no-dhcp-interface=nicI
no-dhcp-interface=lo
bind-interfaces
helps.
This is what I can get to work with 2.53rc1:
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
...
dnsmasq 15815 nobody 5u IPv4 62116 0t0 UDP *:67
dnsmasq 15815 nobody 6u IPv4 62130 0t0 UDP *:53
dnsmasq 15815 nobody 7u IPv4 62131 0t0 TCP *:53 (LISTEN)
dnsmasq 15815 nobody 8u IPv6 62132 0t0 UDP *:53
dnsmasq 15815 nobody 9u IPv6 62133 0t0 TCP *:53 (LISTEN)
...
named 15868 named 20u IPv4 62345 0t0 TCP 127.0.0.1:953 (LISTEN)
named 15868 named 512u IPv4 62331 0t0 UDP 127.0.0.1:53
named 15868 named 513u IPv4 62333 0t0 UDP 127.0.0.24:53
named 15868 named 514u IPv4 62335 0t0 UDP 127.0.0.25:53
named 15868 named 515u IPv4 62337 0t0 UDP 127.0.0.53:53
named 15868 named 516u IPv4 62339 0t0 UDP 95.88.27.175:53
named 15868 named 517u IPv6 62341 0t0 UDP [::1]:53
2.53rc2 doesn't let me use named/IPv6/udp/53. I switched that off, but
I'd like to have IPv6 name resolution through my 6-to-4 tunnel if
possible. bind-9, when starting after dnsmasq, has less trouble,
propably because it binds particular IPs. OTOH, I cannot let dnsmasq
bind like this, because the interfaces it is to handle come and go
(wlan).
I'd very much like dnsmasq to say what port/adress family makes trouble.
clemens
More information about the Dnsmasq-discuss
mailing list