Hello,
Try this:
local-address=127.0.0.1
local-ipv6=::1
there is no option "local-ipv6" in pdns recursor:
http://doc.powerdns.com/built-in-recursor.html
local-address=::1,127.0.0.1 is partially working: pdns listens on ::1
and 127.0.0.1. But it only answers on 127.0.0.1, not ::1 when both ip
addresses are specified.
Could someone please try running pdns recursor with this config file:
setuid=pdns
setgid=pdns
local-address=::1,127.0.0.1
max-negative-ttl=5
allow-from=0.0.0.0/0
You can also use
local-address=127.0.0.1,::1
order doesn't seem to change the symptom.
# netstat -plntu | grep 53
tcp 0 0 127.0.0.1:53 0.0.0.0:*
LISTEN 673/pdns_recursor
tcp 0 0 ::1:53 :::*
LISTEN 673/pdns_recursor
udp 0 0 127.0.0.1:53 0.0.0.0:*
673/pdns_recursor
udp 0 0 ::1:53 :::*
673/pdns_recursor
So pdns recursor is definetely binding to the sockets as specified.
But if you do a
dig google.com @::1
you won't get any answer (at least I don't on a CentOS 5 system with
firewalls disabled for testing).
dig google.com @127.0.0.1
does work however.
Should I file a bug report?
Kind regards
Marten
_______________________________________________
Pdns-users mailing list
[email protected]
http://mailman.powerdns.com/mailman/listinfo/pdns-users
