rec_channel.cc rec_channel.hh \
rec_control.cc \
settings/cxxsupport.cc \
- threadname.cc threadname.hh \
sillyrecords.cc \
sortlist.cc sortlist.hh \
svc-records.cc svc-records.hh \
+ threadname.cc threadname.hh \
unix_utility.cc
nodist_rec_control_SOURCES = \
static bool s_selfResolveCheck;
};
- ComboAddress fromNameOrIP(const string& str, uint16_t defPort, Logr::log_t log);
+ComboAddress fromNameOrIP(const string& str, uint16_t defPort, Logr::log_t log);
}
seedFile: string
If ``addresses`` is empty, the ``name`` field specifies the path name of the RPZ, otherwise the ``name`` field defines the name of the RPZ.
+Starting with version 5.2.0, names instead of IP addresess can be used for ``addresses`` if
+:ref:`setting-yaml-recursor.system_resolver_ttl` is set.
An example of an ``rpzs`` entry, which is a sequence of `RPZ`_:
recurse: bool, default false
notify: bool, default false
+Names instead of IP addresess can be used for ``addresses`` if :ref:`setting-yaml-recursor.system_resolver_ttl` is set.
An example of a :ref:`setting-yaml-recursor.forwarding_catalog_zones` entry, which is a sequence of `ForwardingCatalogZone`_:
.. code-block:: yaml
if !self.xfr.addresses.is_empty() {
validate_address_family(&(field.to_owned() + ".xfr.addresses"), &(field.to_owned() + ".xfr.localAddress"), &self.xfr.addresses, &self.xfr.localAddress)?;
}
+ else {
+ let msg = format!("{}.xfr.addresses: at least one address required", field);
+ return Err(ValidationError { msg });
+ }
Ok(())
}
incoming:
allow_notify_from: [127.0.0.0/8]
recursor:
+ system_resolver_ttl: 30
forwarding_catalog_zones:
- zone: forward.catz
xfr:
# The first server is a bogus one, to test that we correctly fail over to the second one
- addresses: [127.0.0.1:9999, 127.0.0.1:%d]
+ addresses: [127.0.0.1:9999, localhost:%d]
refresh: 1
notify_allowed: true
groups:
- - name: ''
- forwarders: [1.2.3.4]
+ - forwarders: [1.2.3.4] # Default
- name: 'GROUP'
forwarders: [4.5.6.7]
notify_allowed: true