.. class:: DynBPFFilter
- Represents an dynamic eBPF filter, allowing the use of ephemeral rules to an existing eBPF filter. Note that since 1.6.0 the default BPF filter set via :func:`setDefaultBPFFilter` will automatically be used by a :ref:`DynBlockRulesGroup`, becoming the preferred way of dealing with ephemeral rules.
+ Represents a dynamic eBPF filter, allowing the use of ephemeral rules to an existing eBPF filter. Note that since 1.6.0 the default BPF filter set via :func:`setDefaultBPFFilter` will automatically be used by a :ref:`DynBlockRulesGroup`, becoming the preferred way of dealing with ephemeral rules.
.. method:: DynBPFFilter:purgeExpired()
.. method:: DNSDistProtoBufMessage:toDebugString() -> string
- Return an string containing the content of the message
+ Return a string containing the content of the message
:tags: Internals, Bug Fixes
:pullreq: 9302
- Kill an signed vs unsigned warning on OpenBSD.
+ Kill a signed vs unsigned warning on OpenBSD.
.. change::
:tags: Improvements
:pullreq: 12418
:tickets: 12374
- Make cache cleaning of record an negative cache more fair when under pressure.
+ Make cache cleaning of record a negative cache more fair when under pressure.
.. change::
:tags: Bug Fixes
Additionally, the Recursor *can* log to syslog on these systems.
Logging to syslog is disabled in the unit file to prevent double logging.
-To enable this, create an drop in unit file at ``/etc/systemd/systemd/pdns-recursor.service.d/use-syslog.conf``::
+To enable this, create a drop in unit file at ``/etc/systemd/systemd/pdns-recursor.service.d/use-syslog.conf``::
[Service]
ExecStart=
------------------------------
If `recursor.include_dir`_ is set, all ``.yml`` files in it will be processed in alphabetical order, modifying the settings processed so far.
-For simple values like an boolean or number setting, a value in the processed file will overwrite an existing setting.
+For simple values like a boolean or number setting, a value in the processed file will overwrite an existing setting.
For values of type sequence, the new value will *replace* the existing value if the existing value is equal to the ``default`` or if the new value is marked with the ``!override`` tag.
Otherwise, the existing value will be *extended* with the new value by appending the new sequence to the existing.
forwarders:
- '::2'
- The result will *not* be a a single forward with two IP addresses, but two entries for ``example.net``.
+ The result will *not* be a single forward with two IP addresses, but two entries for ``example.net``.
It depends on the specific setting how the sequence is processed and interpreted further.
Description of YAML syntax for structured types
When authoritative for a domain and sure that the entire record does not
-exist, an no referral NS is available, send an empty packet with 'NXDOMAIN'
+exist, a no referral NS is available, send an empty packet with 'NXDOMAIN'
in the flags ('data error').