Skip Menu |

This queue is for tickets about the Net-DNS CPAN distribution.

Report information
The Basics
Id: 95738
Status: resolved
Priority: 0/
Queue: Net-DNS
People
Owner: Nobody in particular
Requestors: SREZIC [...] cpan.org
Cc:
AdminCc:
Bug Information
Severity: (no value)
Broken in: 0.75
Fixed in: (no value)

History Show all quoted text
  Sat May 17 12:07:50 2014 SREZIC [...] cpan.org - Ticket created
Subject: Test failure due to IPv6 servers in /etc/resolv.conf (?)
See http://www.cpantesters.org/cpan/report/400619ec-ddc3-11e3-b672-b88fe0bfc7aa for a sample fail report. This system has three IPv4 and three IPv6 addresses configured in /etc/resolv.conf, and IO::Socket::INET6 is not installed. It seems that the Net::DNS::Resolver object picked one of the IPv6 addresses (debugger output looks like this, IPv6 address is scrambled): DB<3> x $res 0 Net::DNS::Resolver=HASH(0x2b6f398) ... 'nameservers' => ARRAY(0x27ba768) 0 'XXXX:XXX:0:XXXX::XXX:XXXX' ... and the ->nameservers call later failed because of IO::Socket::INET6 not being installed. Regards, Slaven
  Sun May 18 18:28:41 2014 rwfranks [...] acm.org - Correspondence added
From: rwfranks [...] acm.org
On Sat May 17 12:07:50 2014, SREZIC wrote: Show quoted text
> See http://www.cpantesters.org/cpan/report/400619ec-ddc3-11e3-b672- > b88fe0bfc7aa for a sample fail report.
Thanks for confirming my suspicion that the 8 test failures to date are IPv6 related. This is part of a more general resolv.conf parsing problem (RT#95569) and the prickly issue of how to deal with mixed IPv4 and IPv6 nameserver addresses (RT#79568). The failing test also has a flaw!
  Sun May 18 18:28:41 2014 The RT System itself - Status changed from 'new' to 'open'
  Wed Jun 25 05:09:05 2014 NLNETLABS [...] cpan.org - Correspondence added
Fixed in 0.76
  Wed Jun 25 05:09:06 2014 NLNETLABS [...] cpan.org - Status changed from 'open' to 'resolved'