named-checkzone with multiple $ORIGIN
Reindl Harald
h.reindl at thelounge.net
Mon Jun 5 12:45:41 UTC 2017
Am 05.06.2017 um 14:36 schrieb Bernard Fay:
> Sorry keyboard problem...
>
>
> I took control of a DNS based on Bind 9.9. One of the zone files have
> multiple $ORIGIN for example:
>
> $ORIGIN example.com
> ...
> $ORIGIN sub1.example.com
> ...
> $ORIGIN sub2.example.com <http://sub2.example.com>
> ...
> $ORIGIN sub3.example.com <http://sub3.example.com>
> ...
>
>
> While checking the zone file with:
> named-checkzone example.com <http://example.com> example.com.zone
> named-checkzone returns ok for the first $ORIGIN.
>
> But doing
> named-checkzone sub1.example.com <http://example.com> example.com.zone
> named-checkzone sub2.example.com <http://example.com> example.com.zone
> named-checkzone sub3.example.com <http://example.com> example.com.zone
> named-checkzone reports many "ignoring out-of-zone data (....example.com
> <http://example.com>)"
>
> Using multiple $ORIGIN in a single zone file works but named-checkzone
> does not seem to like the idea.
>
> Is there something wrong by using multiple $ORIGIN in a single zone file
> or my understanding of named-checkzone is wrong?
you strip way too much from your config as well as input/output of
named-checkzone and the mess in the quoting above is the result of HTML
converted to sane plaintext as typically encouraged on lists
what is the purpose of obfuscate 'DNS DATA* that much?
More information about the bind-users
mailing list