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

MacPorts noreply at macports.org
Fri Mar 19 21:59:26 UTC 2021


#62494: dns-server can create a duplicate "domain" zone in named.conf
-----------------------------+-----------------------
  Reporter:  steven-michaud  |      Owner:  essandess
      Type:  defect          |     Status:  assigned
  Priority:  Normal          |  Milestone:
 Component:  ports           |    Version:
Resolution:                  |   Keywords:
      Port:  dns-server      |
-----------------------------+-----------------------

Comment (by essandess):

 Steven, Thank you for posting these {{{dns-server}}} issues.

 For context, {{{dns-server}}} is intended to provide a basic, vanilla,
 {{{bind9}}} configuration that users will modify for their own networks.

 The install process ''should'' create a {{{named.conf}}} file with
 settings inferred from your local network at the time of install, apply
 them to the template {{{named.conf.macports}}}, and if it gets it wrong,
 then one has to edit {{{named.conf}}} to fix and/or modify things to suit
 your own network. You own the {{{named.conf}}} file, and MacPorts owns the
 {{{named.conf.macports}}} template file.

 I’m pretty sure that {{{bind9}}} will throw an error if it’s fed the raw
 {{{named.conf.macports}}} file with those {{{@}}} signs and without any
 substitutions for {{{@tld@}}} and so forth. Is that what you’re seeing?

 If you edit in actual domain.tld values, this {{{named.conf}}} file works.

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


More information about the macports-tickets mailing list