NOTICE: This package has been removed from pkgsrc

./net/bind99, Berkeley Internet Name Daemon implementation of DNS, version 9.9

[ CVSweb ] [ Homepage ] [ RSS ] [ Required by ]


Branch: CURRENT, Version: 9.9.13pl1nb2, Package name: bind-9.9.13pl1nb2, Maintainer: pkgsrc-users

BIND, the Berkeley Internet Name Daemon, version 9 is a major rewrite
of nearly all aspects of the underlying BIND architecture. Some
of the important features of BIND-9 are:

- DNS Security
- IP version 6
- DNS Protocol Enhancements
- Views
- Multiprocessor Support
- Improved Portability Architecture
- Full NSEC3 support
- Automatic zone re-signing
- New update-policy methods tcp-self and 6to4-self

This package contains the BIND 9.9 release.


Required to build:
[pkgtools/cwrappers]

Package options: inet6, readline, threads

Master sites:

SHA1: fdc8572a5bde8c25054924cacc8e21f342ff3231
RMD160: 105a3364bd076d9ba59b64fc4571a397b0d4fa12
Filesize: 8548.002 KB

Version history: (Expand)


CVS history: (Expand)


   2018-10-20 19:47:57 by Takahiro Kambe | Files touched by this commit (1)
Log message:
net/bind99: remove a left file

Remove a left file.
   2018-09-23 16:31:11 by Takahiro Kambe | Files touched by this commit (21) | Package removed
Log message:
net/bind99: remove bind99

Remove bind99 from pkgsrc since BIND 9.9 became EOL on 30 June 2018.
   2018-09-13 04:57:43 by John Klos | Files touched by this commit (4)
Log message:
Disable atomic operations on VAX and m68k in addition to mipsel so BIND
compiles on these architectures.
   2018-08-22 11:48:07 by Thomas Klausner | Files touched by this commit (3558)
Log message:
Recursive bump for perl5-5.28.0
   2018-08-13 15:36:25 by Maya Rashish | Files touched by this commit (3) | Package updated
Log message:
bind99: Make ENOBUFS a soft error. Needed for netbsd>=8.
See https://gitlab.isc.org/isc-projects/bind9/issues/462
bump PKGREVISION
   2018-08-09 16:51:25 by Takahiro Kambe | Files touched by this commit (2) | Package updated
Log message:
net/bind99: update to 9.9.13pl1

Update bind99 to 9.9.13pl1 (9.9.13-P1).

	--- 9.9.13-P1 released ---

4997.	[security]	named could crash during recursive processing
			of DNAME records when "deny-answer-aliases" was
			in use. (CVE-2018-5740) [GL #387]
   2018-07-14 05:56:28 by Takahiro Kambe | Files touched by this commit (3) | Package updated
Log message:
net/bind99: update to 9.9.13

This release contains security fix for CVE-2018-5738 and several bug fixes.
For more detail, please refer CHANGES file.
   2018-03-24 16:03:54 by Takahiro Kambe | Files touched by this commit (4) | Package updated
Log message:
net/bind99: update to 9.9.12

New maintenance releases in the 9.9, 9.10, 9.11, and 9.12 branches of
BIND are now available.

Release notes can be found with the releases or in the ISC Knowledge Base:

 9.9.12:  https://kb.isc.org/article/AA-01596/0/9.9.12-Notes.html
 9.10.7:  https://kb.isc.org/article/AA-01595/0/9.10.7-Notes.html
 9.11.3:  https://kb.isc.org/article/AA-01597/0/9.11.3-Notes.html
 9.12.1:  https://kb.isc.org/article/AA-01598/0/9.12.1-Notes.html

Users who are migrating an existing BIND configuration to these new
versions should take special note of two changes in the behavior
of the "update-policy" statement which slightly change the behavior
of two update-policy options.

The first such change is discussed in greater length in the BIND
Operational Notification issued today:

https://kb.isc.org/article/AA-01599/upd … sleadingly

The second change to update-policy behavior concerns this change:

   "update-policy rules that otherwise ignore the name field now
   require that it be set to "." to ensure that any type list present
   is properly interpreted. Previously, if the name field was omitted
   from the rule declaration but a type list was present, it wouldn't
   be interpreted as expected."

which is a correction to an ambiguous case that was previously allowed,
but which was capable of causing unexpected results when accidentally
applied.  The new requirement eliminates is intended to eliminate the
confusion, which previously caused some operators to misapply security
policies.  However, due to the new requirement, named configuration
files that relied on the previous behavior will no longer be accepted.

These changes should not affect most operators, even those using
"update-policy" to define Dynamic DNS permissions, but we would like
to draw your attention to them so that operators are informed about
the new behaviors.