arya dradjica

Migrated some DNSSEC related commits to `new-base`, and had to force-push to resolve some mistakes during the cherry-pick.

@ximon18: I agree that the user experience here isn't the best. But the parsing system has a lot of inherent limitations with regards to error reporting. It can only report...

I think I misunderstood the use case you're thinking about. I was considering this API from the perspective of a user manually executing a program that is loading a zonefile...

My concern is, DNS operators are probably not writing zonefiles by hand; if they're generating it from an automated system, and the output is malformed (at least according to this...

> We will then ask them "which record caused the error" and they will not know [...] The parse error still reports the line number, so it's possible to find...

I'm not sure this is the best way to do it, because this will remove examples from the documentation entirely, increasing confusion. This wouldn't be an issue for docs.rs, but...

That's definitely a bug, and I'll look into fixing it. More generally, I understand that we'd want some more helpful errors for end-users, but I want to be careful about...