mir/bind
2
0
Fork 0
mirror of https://gitlab.isc.org/isc-projects/bind9 synced 2025-08-29 13:38:26 +00:00
Code Issues Releases Wiki Activity

[35925] add more EDNS EXPIRE doc, clarify CHANGES note 3911

Browse Source
This commit is contained in:
Evan Hunt 2014-08-05 19:32:46 -07:00
parent f38a398033
commit d0ffef73fd
3 changed files with 19 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
CHANGES
View File

@ -1,4 +1,7 @@
3911. [func] Implement EDNS EXPIRE option client side. [RT #35925]
3911. [func] Implement EDNS EXPIRE option client side, allowing
a slave server to set the expiration timer correctly
when transferring zone data from another slave
server. [RT #35925]
3910. [bug] Fix races to free event during shutdown. [RT#36720]

8
README
View File

@ -56,6 +56,10 @@ BIND 9.11.0
BIND 9.11.0 includes a number of changes from BIND 9.10 and earlier
releases. New features include:
- The EDNS EXPIRE option has been implemented on the client
side, allowing a slave server to set the expiration timer
correctly when transferring zone data from another slave
server.
- A new "masterfile-style" zone option controls the formatting
of text zone files: When set to "full", a zone file is dumped
in single-line-per-record format.
@ -71,8 +75,8 @@ BIND 9.11.0
- "named -L <filename>" causes named to send log messages to
the specified file by default instead of to the system log.
This release addresses the security flaw described in
CVE-2014-3214 and CVE-2014-3859.
This release addresses the security flaw described in
CVE-2014-3214 and CVE-2014-3859.
BIND 9.10.0

11
doc/arm/Bv9ARM-book.xml
View File

@ -10509,8 +10509,15 @@ rate-limit {
<para>
The <command>request-expire</command> clause determines
whether the local server, acting as a slave, will request
the EDNS EXPIRE value.
whether the local server, when acting as a slave, will
request the EDNS EXPIRE value. The EDNS EXPIRE value
indicates the remaining time before the zone data will
expire and need to be be refreshed. This is used
when a secondary server transfers a zone from another
secondary server; when transferring from the primary, the
expiration timer is set from the EXPIRE field of the SOA
record instead.
The default is <command>yes</command>.
</para>
<para>