[MacPorts] #62494: dns-server can create a duplicate "domain" zone in named.conf
MacPorts
noreply at macports.org
Fri Mar 19 23:49:19 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 steven-michaud):
I should add that I'm already running my own local DNS server (the one
from macOS Server 5.3.1 running on macOS 10.12.6) on my local network. In
that environment my test server ("frankenserver") has a full hostname
(i.e. "frankenserver.bagend.private"), including a "domain" and a "tld".
That probably wouldn't have been the case if I hadn't already been running
a DNS server. In that case the test machine's hostname would presumably
have been something like "frankenserver.local". And I probably wouldn't
have ended up with two identical "bagend.private" zones in the
{{{named.conf}}} generated by {{{dns-server}}}'s script(s).
So this bug is a special case, and not as important as I first thought.
Still, though, it'd be nice if you could add a workaround for this special
case.
--
Ticket URL: <https://trac.macports.org/ticket/62494#comment:5>
MacPorts <https://www.macports.org/>
Ports system for macOS
More information about the macports-tickets
mailing list