[MacPorts] #62494: dns-server can create a duplicate "domain" zone in named.conf

[MacPorts]

#62494: dns-server can create a duplicate "domain" zone in named.conf
-----------------------------+--------------------
  Reporter:  steven-michaud  |      Owner:  (none)
      Type:  defect          |     Status:  new
  Priority:  Normal          |  Milestone:
 Component:  ports           |    Version:
Resolution:                  |   Keywords:
      Port:  dns-server      |
-----------------------------+--------------------
Description changed by steven-michaud:

Old description:

> I've used dns-server to install and configure bind9 on a test server on
> my local (private) network. Its domain name includes the "private" TLD --
> "bagend.private". "named.conf.macports" contains the following two
> "zones":
>
> {{{
> zone "@domain at .private" IN {
>         type master;
>         file "db. at domain@.private";
>         allow-transfer {
>                 none;
>         };
>         allow-update {
>                 none;
>         };
> };
> }}}
>
> {{{
> zone "@domain at .@tld@" IN {
>         type master;
>         file "db. at domain@. at tld@";
>         allow-transfer {
>                 none;
>         };
>         allow-update {
>                 none;
>         };
> };
> }}}
>
> On my system this results in two identical zones being created in
> "named.conf". This is an error, and bind9 refuses to load until I remove
> one of them.

New description:

 I've used dns-server to install and configure bind9 on a test server on my
 local (private) network. Its domain name includes the "private" TLD --
 "bagend.private". "named.conf.macports" contains the following two
 "zones":

 {{{
 zone "@domain at .private" IN {
         type master;
         file "db. at domain@.private";
         allow-transfer {
                 none;
         };
         allow-update {
                 none;
         };
 };
 }}}

 {{{
 zone "@domain at .@tld@" IN {
         type master;
         file "db. at domain@. at tld@";
         allow-transfer {
                 none;
         };
         allow-update {
                 none;
         };
 };
 }}}

 On my system this results in two identical zones being created in
 "named.conf". This is an error, and bind9 refuses to load until I remove
 one of them.

 I'm working on macOS 11.2.3. My MacPorts bind9 distro is "bind9 @9.16.12".

--

-- 
Ticket URL: <https://trac.macports.org/ticket/62494#comment:1>
MacPorts <https://www.macports.org/>
Ports system for macOS