mir/kea
2
0
Fork 0
mirror of https://gitlab.isc.org/isc-projects/kea synced 2025-08-31 14:05:33 +00:00
Code Issues Releases Wiki Activity

[2005] updated the DDNS_UPDATE_NOTIFY_FAIL case

Browse Source
This commit is contained in:
JINMEI Tatuya
2012-06-18 15:05:19 -07:00
parent 32751469f3
commit feca331486
1 changed files with 10 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

11
doc/guide/bind10-guide.xml
View File

@@ -1966,6 +1966,13 @@ what is XfroutClient xfr_client??
update forwarding for secondary zones.
If it receives an update request for a secondary zone, it will
immediately return a response with an RCODE of NOTIMP.
<note><simpara>
For feature completeness update forwarding should be
eventually supported. But right now it's considered a lower
priority task and there is no specific plan of implementing
this feature.
<!-- See Trac #2063 -->
</simpara></note>
</para>
<section>
@@ -1978,7 +1985,9 @@ what is XfroutClient xfr_client??
In addition, <command>b10-xfrout</command> should also be
configured to run; otherwise the notification after an update
(see above) will fail with a timeout, suspending the DDNS
service while <command>b10-ddns</command> waits for the response.
service while <command>b10-ddns</command> waits for the
response (see the description of the DDNS_UPDATE_NOTIFY_FAIL
for further details).
If BIND 10 is already configured to provide authoritative DNS
service they should normally be configured to run already.
</para>