Bug #78878 for Net-DNS:

Thu Aug 09 19:23:08 2012 jhuysing [...] gmail.com - Ticket created

Running Net::DNS ver 8.68 This example fails with "no nameserver" when I run this. (replaced example.com with a valid domain for our network) resolve.conf has nameserver localhost Dig and host both return valid results use Net::DNS; my $res = Net::DNS::Resolver->new; my $query = $res->query("example.com", "SOA"); if ($query) { ($query->answer)[0]->print; } else { print "query failed: ", $res->errorstring, "\n"; }

Thu Aug 23 10:03:41 2012 NLNETLABS [...] cpan.org - Correspondence added

Hi John, Unfortunately I was unable to reproduce your problem. Does it report an error message? Does it also occur if you have "nameserver 127.0.0.1" in /etc/resolv.conf i.s.o. "nameserver localhost"? On Thu 09 Aug 2012 19:23:08, jhuysing@gmail.com wrote: Show quoted text

> Running Net::DNS ver 8.68 > > This example fails with "no nameserver" when I run this. > (replaced example.com with a valid domain for our network) > > resolve.conf has nameserver localhost > > > Dig and host both return valid results > > use Net::DNS; > my $res = Net::DNS::Resolver->new; > my $query = $res->query("example.com", "SOA"); > > if ($query) { > ($query->answer)[0]->print; > } else { > print "query failed: ", $res->errorstring, "\n"; > } >

Thu Aug 23 10:03:42 2012 The RT System itself - Status changed from 'new' to 'open'

Thu Aug 30 00:06:18 2012 jhuysing [...] gmail.com - Correspondence added

Subject:	Re: [rt.cpan.org #78878]
Date:	Thu, 30 Aug 2012 14:06:03 +1000
To:	bug-Net-DNS [...] rt.cpan.org
From:	John huysing <jhuysing [...] gmail.com>

Problem sort of solved Vendor scripts had configured resolve.conf on server with "localhost" instead of 127.0.0.1. Have modifed Net::DNS to check for "localhost" and replace it with 127.0.0.1 or ::1. On 24 August 2012 00:03, NLnet Labs via RT <bug-Net-DNS@rt.cpan.org> wrote: Show quoted text

> <URL: https://rt.cpan.org/Ticket/Display.html?id=78878 > > > Hi John, > > Unfortunately I was unable to reproduce your problem. Does it report an > error message? Does it also occur if you have "nameserver 127.0.0.1" in > /etc/resolv.conf i.s.o. "nameserver localhost"? > > > > On Thu 09 Aug 2012 19:23:08, jhuysing@gmail.com wrote:

> > Running Net::DNS ver 8.68 > > > > This example fails with "no nameserver" when I run this. > > (replaced example.com with a valid domain for our network) > > > > resolve.conf has nameserver localhost > > > > > > Dig and host both return valid results > > > > use Net::DNS; > > my $res = Net::DNS::Resolver->new; > > my $query = $res->query("example.com", "SOA"); > > > > if ($query) { > > ($query->answer)[0]->print; > > } else { > > print "query failed: ", $res->errorstring, "\n"; > > } > >

> > > >

Thu Aug 30 22:56:25 2012 bbb [...] cpan.org - Correspondence added

Subject:	Re: [rt.cpan.org #78878]
Date:	Thu, 30 Aug 2012 20:56:16 -0600
To:	bug-Net-DNS [...] rt.cpan.org
From:	Rob Brown <bbb [...] cpan.org>

The line "nameserver localhost" is not a valid resolv.conf entry. It whole point of resolv is to resolve names into ips, so having a name for a nameserver is rather cyclical and confusing anyways. On Wed, Aug 29, 2012 at 10:06 PM, John huysing via RT <bug-Net-DNS@rt.cpan.org> wrote: Show quoted text

> Queue: Net-DNS > Ticket <URL: https://rt.cpan.org/Ticket/Display.html?id=78878 > > > Problem sort of solved > > Vendor scripts had configured resolve.conf on server with "localhost" > instead of 127.0.0.1. > > Have modifed Net::DNS to check for "localhost" and replace it with > 127.0.0.1 or ::1. > > > On 24 August 2012 00:03, NLnet Labs via RT <bug-Net-DNS@rt.cpan.org> wrote: >

>> <URL: https://rt.cpan.org/Ticket/Display.html?id=78878 > >> >> Hi John, >> >> Unfortunately I was unable to reproduce your problem. Does it report an >> error message? Does it also occur if you have "nameserver 127.0.0.1" in >> /etc/resolv.conf i.s.o. "nameserver localhost"? >> >> >> >> On Thu 09 Aug 2012 19:23:08, jhuysing@gmail.com wrote:

>> > Running Net::DNS ver 8.68 >> > >> > This example fails with "no nameserver" when I run this. >> > (replaced example.com with a valid domain for our network) >> > >> > resolve.conf has nameserver localhost >> > >> > >> > Dig and host both return valid results >> > >> > use Net::DNS; >> > my $res = Net::DNS::Resolver->new; >> > my $query = $res->query("example.com", "SOA"); >> > >> > if ($query) { >> > ($query->answer)[0]->print; >> > } else { >> > print "query failed: ", $res->errorstring, "\n"; >> > } >> >

>> >> >> >>

>

Fri Aug 31 08:42:56 2012 NLNETLABS [...] cpan.org - Correspondence added

On Thu 30 Aug 2012 22:56:25, BBB wrote: Show quoted text

> The line "nameserver localhost" is not a valid resolv.conf entry. It > whole point of resolv is to resolve names into ips, so having a name > for a nameserver is rather cyclical and confusing anyways.

I agree. Closing ticket.

Fri Aug 31 08:42:57 2012 NLNETLABS [...] cpan.org - Status changed from 'open' to 'rejected'