Commit 5e08967f authored by JINMEI Tatuya's avatar JINMEI Tatuya
Browse files

[2911] update log message on multi-SOA to match the latest behavior.

it now unconditionally uses AXFR, so mentioning possible failure of IXFR
doesn't make sense.
parent cd6f223e
......@@ -279,9 +279,9 @@ On starting an xfrin session, it is identified that the zone to be
transferred has multiple SOA RRs. Such a zone is broken, but could be
accidentally configured especially in a data source using "non
captive" backend database. The implementation ignores entire SOA RRs
and tries to continue processing as if the zone were empty. This
means subsequent AXFR can succeed and possibly replace the zone with
valid content, but an IXFR attempt will fail.
and tries to continue processing as if the zone were empty. This also
means AXFR will be used unconditionally, regardless of the configured value
for request_ixfr of the zone.
% XFRIN_ZONE_NO_SOA Zone %1 does not have SOA
On starting an xfrin session, it is identified that the zone to be
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment