mirror of
https://gitlab.isc.org/isc-projects/bind9
synced 2025-08-31 06:25:31 +00:00
Deduplicate link anchors in the ARM
Some statement names like "allow-query" had manually defined link anchor _allow-query and also implicit anchor created by .. namedconf:statement:: syntax. This causes warnings if a ambiguous reference is made using :any:`allow-query` syntax. Remove (hopefully all) manually defined anchors which pointed to identical place as the implicit anchor. This allows :any: to work. In rare cases where manual anchor points to descriptive text separated from statement definition the reference was disamguated by replacing :any:`notify` with :ref:`notify` (for manual anchor) vs. :namedconf:ref:`notify` (for statement definition). Please note that `options` statement is a trap: It is ambiguous even without manual anchor because rndc.conf has its own `options`. Use :namedconf:ref:`options` vs. :rndcconf:ref:`options` to select appropriate target.
This commit is contained in:
@@ -143,7 +143,7 @@ responses for all users.
|
||||
|
||||
Private IP addresses may be defined using standard :ref:`reverse-mapping
|
||||
techniques<ipv4_reverse>` or using the
|
||||
:ref:`empty-zones-enable<empty-zones-enable>` statement. By
|
||||
:any:`empty-zones-enable` statement. By
|
||||
default this statement is set to ``empty-zones-enable yes;`` and thus automatically prevents
|
||||
unnecessary DNS traffic by sending an NXDOMAIN error response (indicating the
|
||||
name does not exist) to any request. However, some applications may require a
|
||||
@@ -263,8 +263,8 @@ It is therefore a **closed** resolver and cannot be used in wider network attack
|
||||
};
|
||||
|
||||
The :any:`zone` and :any:`acl` blocks, and the
|
||||
:ref:`allow-query<allow-query>`, :ref:`empty-zones-enable<empty-zones-enable>`,
|
||||
:ref:`file<file>`, :ref:`notify<notify_st>`, :ref:`recursion<recursion>`, and
|
||||
:any:`allow-query`, :any:`empty-zones-enable`,
|
||||
:any:`file`, :namedconf:ref:`notify`, :any:`recursion`, and
|
||||
:any:`type` statements are described in detail in the appropriate
|
||||
sections.
|
||||
|
||||
@@ -381,9 +381,9 @@ provided<selective_forward_sample>`.
|
||||
};
|
||||
|
||||
The :any:`zone` and :any:`acl` blocks, and the
|
||||
:ref:`allow-query<allow-query>`, :ref:`empty-zones-enable<empty-zones-enable>`,
|
||||
:ref:`file<file>`, :ref:`forward<forward>`, :ref:`forwarders<forwarders>`,
|
||||
:ref:`notify<notify_st>`, :ref:`recursion<recursion>`, and :any:`type`
|
||||
:any:`allow-query`, :any:`empty-zones-enable`,
|
||||
:any:`file`, :any:`forward`, :any:`forwarders`,
|
||||
:namedconf:ref:`notify`, :any:`recursion`, and :any:`type`
|
||||
statements are described in detail in the appropriate sections.
|
||||
|
||||
As a reminder, the configuration of this forwarding resolver does **not**
|
||||
@@ -508,9 +508,9 @@ those IPs from which it will accept recursive queries.
|
||||
|
||||
|
||||
The :any:`zone` and :any:`acl` blocks, and the
|
||||
:ref:`allow-query<allow-query>`, :ref:`empty-zones-enable<empty-zones-enable>`,
|
||||
:ref:`file<file>`, :ref:`forward<forward>`, :ref:`forwarders<forwarders>`,
|
||||
:ref:`notify<notify_st>`, :ref:`recursion<recursion>`, and :any:`type`
|
||||
:any:`allow-query`, :any:`empty-zones-enable`,
|
||||
:any:`file`, :any:`forward`, :any:`forwarders`,
|
||||
:namedconf:ref:`notify`, :any:`recursion`, and :any:`type`
|
||||
statements are described in detail in the appropriate sections.
|
||||
|
||||
As a reminder, the configuration of this resolver does **not** access the DNS
|
||||
|
Reference in New Issue
Block a user