Support multiple $ORIGINs in one zone file

[jamieparfet]

I have a large zone file containing multiple $ORIGIN entries. Sometimes it declares a new $ORIGIN before switching back to the original, like so:

$ORIGIN example.com
sub1 ...
sub2 ...
$ORIGIN test-env.example.com
testsub1 ...
testsub2 ...
$ORIGIN example.com
sub3 ...
sub4 ...

Would it be possible to implement the parsing of multiple $ORIGINs in one zone file? As far as I can tell, this is RFC compliant (admittedly not best-practice).

Thanks!

[elgs]

I am so sorry I overlooked your issue.

I understand your situation. Conceptually the change should be straightforward, but this would change the structure of the json. From 1 to 5, how badly do you need this feature? If 5, I will implement it.

[elgs]

Actually I think you are right. Every record in the json should have a field called origin. The change should be easy, but I will need to think about potential backward compatibility issues.