ComputerSurge/bind9
3
0
Fork 0
Code Pull Requests 1 Activity

Merge branch '870-add-a-comment-explaining-a-mirror-zone-glitch' into 'master'

Browse Source 
Add a comment explaining a mirror zone glitch

Closes #870

See merge request isc-projects/bind9!1480
This commit is contained in:
Michał Kępień
2019-02-08 05:49:35 -05:00
parent b46b243884 2e4187afd5
commit 60c89a4c85
1 changed files with 10 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
lib/dns/zt.c
View File

@@ -179,6 +179,16 @@ dns_zt_find(dns_zt_t *zt, const dns_name_t *name, unsigned int options,
* a mirror zone which is expired or not yet loaded, treat it
* as non-existent. This will trigger a fallback to recursion
* instead of returning a SERVFAIL.
*
* Note that currently only the deepest match in the zone table
* is checked. Consider a server configured with two mirror
* zones: "bar" and its child, "foo.bar". If zone data is
* available for "bar" but not for "foo.bar", a query with
* QNAME equal to or below "foo.bar" will cause ISC_R_NOTFOUND
* to be returned, not DNS_R_PARTIALMATCH, despite zone data
* being available for "bar". This is considered to be an edge
* case, handling which more appropriately is possible, but
* arguably not worth the added complexity.
*/
if ((options & DNS_ZTFIND_MIRROR) != 0 &&
dns_zone_gettype(dummy) == dns_zone_mirror &&