[Pdns-users] IPv4 and IPv6 sockets at the same time

[Chris Russell]

Hi Martin,

 This may be your version and/or setup.  As a side note, strongly recommend you upgrade to Centos 6, as the ipv6 code in the kernel provided with Centos 5 doesn't perform ipv6 connection tracking properly in terms of the firewall. Does work fine but you need to allow more than you should.

 That aside though,

 Running pdns-recursor-3.3-1 here on Centos 5.6, its working fine for both. Relevant Line from recursor.conf:




local-address=127.0.0.1,ipv4.address, ::1, ipv6.address


[root at www ~]# pdns_recursor --version
version: 3.3

[root at www ~]# dig www.google.com @127.0.0.1

; <<>> DiG 9.3.6-P1-RedHat-9.3.6-4.P1.el5_5.3 <<>> www.google.com @127.0.0.1
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 16222
;; flags: qr rd ra; QUERY: 1, ANSWER: 7, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;www.google.com.                        IN      A

;; ANSWER SECTION:
www.google.com.         86249   IN      CNAME   www.l.google.com.

...
;; SERVER: 127.0.0.1#53(127.0.0.1)


# ipv6

[root at www ~]# dig www.google.com @::1

; <<>> DiG 9.3.6-P1-RedHat-9.3.6-4.P1.el5_5.3 <<>> www.google.com @::1
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 35756
;; flags: qr rd ra; QUERY: 1, ANSWER: 7, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;www.google.com.                        IN      A

;; ANSWER SECTION:
www.google.com.         86400   IN      CNAME   www.l.google.com.

...
;; SERVER: ::1#53(::1)




-----Original Message-----
From: pdns-users-bounces at mailman.powerdns.com [mailto:pdns-users-bounces at mailman.powerdns.com] On Behalf Of Marten Lehmann
Sent: 21 July 2011 12:48
To: pdns-users at mailman.powerdns.com
Subject: Re: [Pdns-users] IPv4 and IPv6 sockets at the same time

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
Pdns-users at mailman.powerdns.com
http://mailman.powerdns.com/mailman/listinfo/pdns-users

Knowledge I.T.
'Unifying Business Technology'
www.knowledgeit.co.uk

Knowledge Limited, Company Registration: 1554385
Registered Office: New Century House, Crowther Road, Washington, Tyne & Wear. NE38 0AQ
Leeds Office: Viscount Court, Leeds Road, Rothwell, Leeds. LS26 0GR

Tel: 0845 142 0020. Fax: 0845 142 0021

E-Mail Disclaimer: This e-mail message is intended to be received only by persons entitled to receive the confidential information it may contain. E-mail messages to clients of Knowledge IT may contain information that is confidential and legally privileged. Please do not read, copy, forward, or store this message unless you are an intended recipient of it. If you have received this message in error, please forward it to the sender and delete it completely from your computer system.

Please consider the environment before printing this email.