Skip Menu |

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

Report information
The Basics
Id: 99879
Status: open
Priority: 0/
Queue: Net-DNS-ZoneFile

People
Owner: Nobody in particular
Requestors: csr1 [...] ziobro.rochester.ny.us
Cc:
AdminCc:

Bug Information
Severity: Wishlist
Broken in: (no value)
Fixed in: (no value)



CC: z <csr1 [...] ziobro.rochester.ny.us>
Subject: Bug in initial handling of origin when no explicit $ORIGIN set
Date: Wed, 29 Oct 2014 05:02:26 -0400
To: bug-Net-DNS-ZoneFile [...] rt.cpan.org
From: z <csr1 [...] ziobro.rochester.ny.us>
I'm running Net::DNS::ZoneFile with the rwfranks fix of 2014/10/07 07:56. Program: use Net::DNS::ZoneFile; $zonefile = new Net::DNS::ZoneFile( $ARGV[0] ); while ( $rr = $zonefile->read ) { $rr->print; } INPUT: @ IN A 0.0.0.0 Should yield: @ IN A 0.0.0.0 but instead returns . 0 IN A 0.0.0.0 The origin should be initialized to "" NOT ".". They are different! The initial @ is determined by the /etc/named.conf file. There is no way to know it just by reading a zone file. Thanks! Ciao, //Z\\ Jim Ziobro
Thanks Jim, Deferring origin evaluation is an interesting idea, but it is a bit harsh to call this a bug :) I would say it is more a feature request. I don't oversee yet the implications, but I can imagine that they could be far-reaching. I've changed the subject & severity to reflect the feature request nature of this ticket. We'll think about it. Thanks again, -- Willem On Wed 29 Oct 2014 05:02:46, csr1@ziobro.rochester.ny.us wrote: Show quoted text
> I'm running Net::DNS::ZoneFile with the rwfranks fix of 2014/10/07 07:56. > > Program: > > use Net::DNS::ZoneFile; > $zonefile = new Net::DNS::ZoneFile( $ARGV[0] ); > while ( $rr = $zonefile->read ) { $rr->print; } > > > INPUT: > @ IN A 0.0.0.0 > > Should yield: > @ IN A 0.0.0.0 > but instead returns > . 0 IN A 0.0.0.0 > > The origin should be initialized to "" NOT ".". They are different! > The initial @ is determined by the /etc/named.conf file. There is no way > to know it just by reading a zone file. > > Thanks! > Ciao, > //Z\\ > Jim Ziobro
Subject: Re: [rt.cpan.org #99879] Postpone handling of origin when no explicit $ORIGIN set
Date: Wed, 29 Oct 2014 09:54:07 -0400
To: bug-Net-DNS-ZoneFile [...] rt.cpan.org
From: Jim Ziobro <james [...] ziobro.info>
My understanding is that the package Net::DNS::ZoneFile is supposed to act like the rest of Net::DNS. (like AXFR?) When talking to a name server the user would have to know the base domain of the query. There simply is no way to know that when reading an arbitrary zone file. It is a conceptual problem in the object model of ZoneFile. Maybe we need an optional arg for opening a zone file (check out axfr call)? I discovered this accidentally when I read my Master files for BIND. My application will access Slave zone files. All files transferred by BIND (Slave files) explicitly include the $ORIGIN. No hurry... Ciao, //Z\\ On 10/29/2014 5:42 AM, NLnet Labs via RT wrote: Show quoted text
> <URL: https://rt.cpan.org/Ticket/Display.html?id=99879 > > > Thanks Jim, > > Deferring origin evaluation is an interesting idea, but it is a bit harsh to call this a bug :) > I would say it is more a feature request. I don't oversee yet the implications, but I can imagine that they could be far-reaching. > > I've changed the subject & severity to reflect the feature request nature of this ticket. > We'll think about it. Thanks again, > > -- Willem > > On Wed 29 Oct 2014 05:02:46, csr1@ziobro.rochester.ny.us wrote:
>> I'm running Net::DNS::ZoneFile with the rwfranks fix of 2014/10/07 07:56. >> >> Program: >> >> use Net::DNS::ZoneFile; >> $zonefile = new Net::DNS::ZoneFile( $ARGV[0] ); >> while ( $rr = $zonefile->read ) { $rr->print; } >> >> >> INPUT: >> @ IN A 0.0.0.0 >> >> Should yield: >> @ IN A 0.0.0.0 >> but instead returns >> . 0 IN A 0.0.0.0 >> >> The origin should be initialized to "" NOT ".". They are different! >> The initial @ is determined by the /etc/named.conf file. There is no way >> to know it just by reading a zone file. >> >> Thanks! >> Ciao, >> //Z\\ >> Jim Ziobro
>
Subject: Re: [rt.cpan.org #99879] Postpone handling of origin when no explicit $ORIGIN set
Date: Wed, 29 Oct 2014 15:00:48 +0100
To: bug-Net-DNS-ZoneFile [...] rt.cpan.org
From: Willem Toorop <willem [...] nlnetlabs.nl>
Ehm... now you confuse me. You can specify an origin as the second argument of Net::DNS::ZoneFile. I quote from the manpage: "The optional second argument specifies $ORIGIN for the zone file." Op 29-10-14 om 14:54 schreef Jim Ziobro via RT: Show quoted text
> Queue: Net-DNS-ZoneFile > Ticket <URL: https://rt.cpan.org/Ticket/Display.html?id=99879 > > > My understanding is that the package Net::DNS::ZoneFile is supposed to > act like the rest of Net::DNS. (like AXFR?) When talking to a name > server the user would have to know the base domain of the query. There > simply is no way to know that when reading an arbitrary zone file. It is > a conceptual problem in the object model of ZoneFile. > > Maybe we need an optional arg for opening a zone file (check out axfr call)? > > I discovered this accidentally when I read my Master files for BIND. My application will access Slave zone files. All files transferred by BIND (Slave files) explicitly include the $ORIGIN. No hurry... > > Ciao, > //Z\\ > > On 10/29/2014 5:42 AM, NLnet Labs via RT wrote:
>> <URL: https://rt.cpan.org/Ticket/Display.html?id=99879 > >> >> Thanks Jim, >> >> Deferring origin evaluation is an interesting idea, but it is a bit harsh to call this a bug :) >> I would say it is more a feature request. I don't oversee yet the implications, but I can imagine that they could be far-reaching. >> >> I've changed the subject & severity to reflect the feature request nature of this ticket. >> We'll think about it. Thanks again, >> >> -- Willem >> >> On Wed 29 Oct 2014 05:02:46, csr1@ziobro.rochester.ny.us wrote:
>>> I'm running Net::DNS::ZoneFile with the rwfranks fix of 2014/10/07 07:56. >>> >>> Program: >>> >>> use Net::DNS::ZoneFile; >>> $zonefile = new Net::DNS::ZoneFile( $ARGV[0] ); >>> while ( $rr = $zonefile->read ) { $rr->print; } >>> >>> >>> INPUT: >>> @ IN A 0.0.0.0 >>> >>> Should yield: >>> @ IN A 0.0.0.0 >>> but instead returns >>> . 0 IN A 0.0.0.0 >>> >>> The origin should be initialized to "" NOT ".". They are different! >>> The initial @ is determined by the /etc/named.conf file. There is no way >>> to know it just by reading a zone file. >>> >>> Thanks! >>> Ciao, >>> //Z\\ >>> Jim Ziobro
>>
>
Subject: Re: [rt.cpan.org #99879] Postpone handling of origin when no explicit $ORIGIN set
Date: Wed, 29 Oct 2014 10:21:35 -0400
To: bug-Net-DNS-ZoneFile [...] rt.cpan.org
From: Jim Ziobro <james [...] ziobro.info>
My bad! I missed the second argument. Ciao, //Z\\ On 10/29/2014 10:01 AM, Willem Toorop via RT wrote: Show quoted text
> <URL: https://rt.cpan.org/Ticket/Display.html?id=99879 > > > Ehm... now you confuse me. You can specify an origin as the second > argument of Net::DNS::ZoneFile. I quote from the manpage: > > "The optional second argument specifies $ORIGIN for the zone file." > > Op 29-10-14 om 14:54 schreef Jim Ziobro via RT:
>> Queue: Net-DNS-ZoneFile >> Ticket <URL: https://rt.cpan.org/Ticket/Display.html?id=99879 > >> >> My understanding is that the package Net::DNS::ZoneFile is supposed to >> act like the rest of Net::DNS. (like AXFR?) When talking to a name >> server the user would have to know the base domain of the query. There >> simply is no way to know that when reading an arbitrary zone file. It is >> a conceptual problem in the object model of ZoneFile. >> >> Maybe we need an optional arg for opening a zone file (check out axfr call)? >> >> I discovered this accidentally when I read my Master files for BIND. My application will access Slave zone files. All files transferred by BIND (Slave files) explicitly include the $ORIGIN. No hurry... >> >> Ciao, >> //Z\\ >> >> On 10/29/2014 5:42 AM, NLnet Labs via RT wrote:
>>> <URL: https://rt.cpan.org/Ticket/Display.html?id=99879 > >>> >>> Thanks Jim, >>> >>> Deferring origin evaluation is an interesting idea, but it is a bit harsh to call this a bug :) >>> I would say it is more a feature request. I don't oversee yet the implications, but I can imagine that they could be far-reaching. >>> >>> I've changed the subject & severity to reflect the feature request nature of this ticket. >>> We'll think about it. Thanks again, >>> >>> -- Willem >>> >>> On Wed 29 Oct 2014 05:02:46, csr1@ziobro.rochester.ny.us wrote:
>>>> I'm running Net::DNS::ZoneFile with the rwfranks fix of 2014/10/07 07:56. >>>> >>>> Program: >>>> >>>> use Net::DNS::ZoneFile; >>>> $zonefile = new Net::DNS::ZoneFile( $ARGV[0] ); >>>> while ( $rr = $zonefile->read ) { $rr->print; } >>>> >>>> >>>> INPUT: >>>> @ IN A 0.0.0.0 >>>> >>>> Should yield: >>>> @ IN A 0.0.0.0 >>>> but instead returns >>>> . 0 IN A 0.0.0.0 >>>> >>>> The origin should be initialized to "" NOT ".". They are different! >>>> The initial @ is determined by the /etc/named.conf file. There is no way >>>> to know it just by reading a zone file. >>>> >>>> Thanks! >>>> Ciao, >>>> //Z\\ >>>> Jim Ziobro