Skip Menu |

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

Report information
The Basics
Id: 9118
Status: resolved
Priority: 0/
Queue: DNS-ZoneParse

People
Owner: Nobody in particular
Requestors: ravi [...] cow.org
Cc:
AdminCc:

Bug Information
Severity: Important
Broken in: 0.95
Fixed in: (no value)



Subject: $ORIGIN
DNS-ZoneParse-0.95, perl 5.8.5, fbsd 5.2.1 Currently isn't able to parse $ORIGIN lines. I explicitly enter the $ORIGIN before my $TTL for the zone. In addition for in-addr zones that have few entries i'll colapse the zone and have multiple ORIGINS. For example: $ORIGIN 100.10.in-addr.arpa. $TTL 5M [soa...] [ns...] $origin 1.100.10.in-addr.arpa. [...] $origin 2.100.10.in-addr.arpa. [...] $origin 3.100.10.in-addr.arpa. [...] $origin 4.100.10.in-addr.arpa. I guess I could put in all the octets rather than adding a new origin (1.4.100.10 in ptr foo.com.) but i'd like not to if this is a simple patch.
Here's a patch to handle some basic $ORIGIN parsing. I just removed the SOA origin from the $ORIGIN parameter and added it to the 'name' of each record that follows. It isn't ideal, but it worked for my needs. The patch is for 0.96.
Download ZoneParse.pm-patch
application/octet-stream 3.1k

Message body not shown because it is not plain text.

$ORIGIN support was added in 1.0. Looks like I forgot to update this bug, sorry!