[Bug 199384] dns/bind99 suggested patch to /usr/ports/dns/bind99/files/named.in
bugzilla-noreply at freebsd.org
bugzilla-noreply at freebsd.org
Sun Apr 12 02:11:26 UTC 2015
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=199384
Bug ID: 199384
Summary: dns/bind99 suggested patch to
/usr/ports/dns/bind99/files/named.in
Product: Ports & Packages
Version: Latest
Hardware: Any
OS: Any
Status: New
Severity: Affects Some People
Priority: ---
Component: Individual Port(s)
Assignee: mat at FreeBSD.org
Reporter: curtis at ipv6.occnc.com
Flags: maintainer-feedback?(mat at FreeBSD.org)
Assignee: mat at FreeBSD.org
CC:
Created attachment 155489
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=155489&action=edit
patch file for dns/bind99 or dns/bind910
The purpose of this patch is to fix two very minor annoyances.
1. If named.conf is moved in /etc/rc.conf with a line such as
named_conf=/etc/namedb/named.conf, then rndc-confgen creates a
key in the /etc/namedb but /usr/local/etc/rc.d/named restart or
reload won't use that key file. The reload will fail, but the
restart falls back to using kill.
2. The second problem is that if a rndc.conf file is used and put
in /etc/namedb, rndc won't find it. It is necessary to use an
rndc.conf file if running named in a jail, where there is no
127.0.0.1 address or if running IPv6 only and in other
circumstances, such as if it is desirable to reload remotely
(although an ssh command also solves this).
The change is simply to load up a rndc_flags variable and use it in
the two places where rndc is used.
btw- there seems to be a non-ascii character in the comment on line
188 after the string "but ${named_program}".
Patch is attached.
--
You are receiving this mail because:
You are the assignee for the bug.
More information about the freebsd-ports-bugs
mailing list