Rule Actions

Rule Selectors need to be combined with an action for them to actually do something with the matched packets. This page describes the Lua versions of these actions, for the YAML version please see YAML action reference and YAML response-action reference.

Some actions allow further processing of rules, this is noted in their description. Most of these start with ‘Set’ with a few exceptions, mostly for logging actions. These exceptions are:

The following actions exist.

AllowAction()

Let these packets go through.

AllowResponseAction()

Let these packets go through.

ClearRecordTypesResponseAction(types)

Removes given type(s) records from the response. Beware you can accidentally turn the answer into a NODATA response without a SOA record in the additional section in which case you may want to use NegativeAndSOAAction() to generate an answer, see example below. Subsequent rules are processed after this action.

-- removes any HTTPS record in the response
addResponseAction(
        QNameRule('www.example.com.'),
        ClearRecordTypesResponseAction(DNSQType.HTTPS)
)
-- reply directly with NODATA and a SOA record as we know the answer will be empty
addAction(
        AndRule{QNameRule('www.example.com.'), QTypeRule(DNSQType.HTTPS)},
        NegativeAndSOAAction(false, 'example.com.', 3600, 'ns.example.com.', 'postmaster.example.com.', 1, 1800, 900, 604800, 86400)
)
Parameters:

types (int) – a single type or a list of types to remove

ContinueAction(action)

Execute the specified action and override its return with None, making it possible to continue the processing. Subsequent rules are processed after this action.

Parameters:

action (Action) – Any other action

DelayAction(milliseconds)

Delay the response by the specified amount of milliseconds (UDP-only). Note that the sending of the query to the backend, if needed, is not delayed. Only the sending of the response to the client will be delayed. Subsequent rules are processed after this action.

Parameters:

milliseconds (int) – The amount of milliseconds to delay the response

DelayResponseAction(milliseconds)

Delay the response by the specified amount of milliseconds (UDP-only). The only difference between this action and DelayAction() is that they can only be applied on, respectively, responses and queries. Subsequent rules are processed after this action.

Parameters:

milliseconds (int) – The amount of milliseconds to delay the response

DnstapLogAction(identity, logger[, alterFunction])

Send the current query to a remote logger as a dnstap message. alterFunction is a callback, receiving a DNSQuestion and a DnstapMessage, that can be used to modify the message. Subsequent rules are processed after this action.

Parameters:
  • identity (string) – Server identity to store in the dnstap message

  • logger – The FrameStreamLogger or RemoteLogger object to write to

  • alterFunction – A Lua function to alter the message before sending

DnstapLogResponseAction(identity, logger[, alterFunction])

Send the current response to a remote logger as a dnstap message. alterFunction is a callback, receiving a DNSQuestion and a DnstapMessage, that can be used to modify the message. Subsequent rules are processed after this action.

Parameters:
  • identity (string) – Server identity to store in the dnstap message

  • logger – The FrameStreamLogger or RemoteLogger object to write to

  • alterFunction – A Lua function to alter the message before sending

DropAction()

Drop the packet.

DropResponseAction()

Drop the packet.

ERCodeAction(rcode[, options])

Reply immediately by turning the query into a response with the specified EDNS extended rcode. rcode can be specified as an integer or as one of the built-in RCode.

Parameters:
  • rcode (int) – The extended RCODE to respond with.

  • options (table) – A table with key: value pairs with options.

Options:

  • aa: bool - Set the AA bit to this value (true means the bit is set, false means it’s cleared). Default is to clear it.

  • ad: bool - Set the AD bit to this value (true means the bit is set, false means it’s cleared). Default is to clear it.

  • ra: bool - Set the RA bit to this value (true means the bit is set, false means it’s cleared). Default is to copy the value of the RD bit from the incoming query.

HTTPStatusAction(status, body, contentType = ""[, options])

Changed in version 2.0.0: The options parameter is now deprecated.

Return an HTTP response with a status code of ‘’status’’. For HTTP redirects, ‘’body’’ should be the redirect URL.

Parameters:
  • status (int) – The HTTP status code to return.

  • body (string) – The body of the HTTP response, or a URL if the status code is a redirect (3xx).

  • contentType (string) – The HTTP Content-Type header to return for a 200 response, ignored otherwise. Default is ‘’application/dns-message’’.

  • options (table) – A table with key: value pairs with options. Deprecated since 2.0.0 as it had unexpected side-effects.

Options:

  • aa: bool - Set the AA bit to this value (true means the bit is set, false means it’s cleared). Default is to clear it.

  • ad: bool - Set the AD bit to this value (true means the bit is set, false means it’s cleared). Default is to clear it.

  • ra: bool - Set the RA bit to this value (true means the bit is set, false means it’s cleared). Default is to copy the value of the RD bit from the incoming query.

KeyValueStoreLookupAction(kvs, lookupKey, destinationTag)

Does a lookup into the key value store referenced by ‘kvs’ using the key returned by ‘lookupKey’, and storing the result if any into the tag named ‘destinationTag’. The store can be a CDB (newCDBKVStore()) or a LMDB database (newLMDBKVStore()). The key can be based on the qname (KeyValueLookupKeyQName() and KeyValueLookupKeySuffix()), source IP (KeyValueLookupKeySourceIP()) or the value of an existing tag (KeyValueLookupKeyTag()). Subsequent rules are processed after this action. Note that the tag is always created, even if there was no match, but in that case the content is empty.

Parameters:
  • kvs (KeyValueStore) – The key value store to query

  • lookupKey (KeyValueLookupKey) – The key to use for the lookup

  • destinationTag (string) – The name of the tag to store the result into

KeyValueStoreRangeLookupAction(kvs, lookupKey, destinationTag)

Does a range-based lookup into the key value store referenced by ‘kvs’ using the key returned by ‘lookupKey’, and storing the result if any into the tag named ‘destinationTag’. This assumes that there is a key in network byte order for the last element of the range (for example 2001:0db8:ffff:ffff:ffff:ffff:ffff:ffff for 2001:db8::/32) which contains the first element of the range (2001:0db8:0000:0000:0000:0000:0000:0000) (optionally followed by any data) as value, also in network byte order, and that there is no overlapping ranges in the database. This requires that the underlying store supports ordered keys, which is true for LMDB but not for CDB.

Subsequent rules are processed after this action.

Parameters:
  • kvs (KeyValueStore) – The key value store to query

  • lookupKey (KeyValueLookupKey) – The key to use for the lookup

  • destinationTag (string) – The name of the tag to store the result into

LimitTTLResponseAction(min[, max[, types]])

Cap the TTLs of the response to the given boundaries.

Parameters:
  • min (int) – The minimum allowed value

  • max (int) – The maximum allowed value

  • types (table) – The record types to cap the TTL for, as integers. Default is empty which means all records will be capped.

LogAction(
    [filename[, binary[, append[, buffered[, verboseOnly[, includeTimestamp]]]]]]
)

Log a line for each query, to the specified file if any, to the console (require verbose) if the empty string is given as filename.

If an empty string is supplied in the file name, the logging is done to stdout, and only in verbose mode by default. This can be changed by setting verboseOnly to false.

When logging to a file, the binary optional parameter specifies whether we log in binary form (default) or in textual form. Before 1.4.0 the binary log format only included the qname and qtype. Since 1.4.0 it includes an optional timestamp, the query ID, qname, qtype, remote address and port.

The append optional parameter specifies whether we open the file for appending or truncate each time (default). The buffered optional parameter specifies whether writes to the file are buffered (default) or not.

Since 1.7.0 calling the reload() method on the object will cause it to close and re-open the log file, for rotation purposes.

Subsequent rules are processed after this action.

Parameters:
  • filename (string) – File to log to. Set to an empty string to log to the normal stdout log, this only works when -v is set on the command line.

  • binary (bool) – Do binary logging. Default true

  • append (bool) – Append to the log. Default false

  • buffered (bool) – Use buffered I/O. Default true

  • verboseOnly (bool) – Whether to log only in verbose mode when logging to stdout. Default is true

  • includeTimestamp (bool) – Whether to include a timestamp for every entry. Default is false

LogResponseAction(
    [filename[, append[, buffered[, verboseOnly[, includeTimestamp]]]]]]
)

Log a line for each response, to the specified file if any, to the console (require verbose) if the empty string is given as filename.

If an empty string is supplied in the file name, the logging is done to stdout, and only in verbose mode by default. This can be changed by setting verboseOnly to false.

The append optional parameter specifies whether we open the file for appending or truncate each time (default). The buffered optional parameter specifies whether writes to the file are buffered (default) or not.

Since 1.7.0 calling the reload() method on the object will cause it to close and re-open the log file, for rotation purposes.

Subsequent rules are processed after this action.

Parameters:
  • filename (string) – File to log to. Set to an empty string to log to the normal stdout log, this only works when -v is set on the command line.

  • append (bool) – Append to the log. Default false

  • buffered (bool) – Use buffered I/O. Default true

  • verboseOnly (bool) – Whether to log only in verbose mode when logging to stdout. Default is true

  • includeTimestamp (bool) – Whether to include a timestamp for every entry. Default is false

LuaAction(function)

Invoke a Lua function that accepts a DNSQuestion.

The function should return a DNSAction. If the Lua code fails, ServFail is returned.

Parameters:

function (string) – the name of a Lua function

LuaFFIAction(function)

Invoke a Lua FFI function that accepts a pointer to a dnsdist_ffi_dnsquestion_t object, whose bindings are defined in dnsdist-lua-ffi-interface.h.

The function should return a DNSAction. If the Lua code fails, ServFail is returned.

Parameters:

function (string) – the name of a Lua function

LuaFFIPerThreadAction(function)

Invoke a Lua FFI function that accepts a pointer to a dnsdist_ffi_dnsquestion_t object, whose bindings are defined in dnsdist-lua-ffi-interface.h.

The function should return a DNSAction. If the Lua code fails, ServFail is returned.

The function will be invoked in a per-thread Lua state, without access to the global Lua state. All constants (DNSQType, RCode, …) are available in that per-thread context, as well as all FFI functions. Objects and their bindings that are not usable in a FFI context (DNSQuestion, DNSDistProtoBufMessage, PacketCache, …) are not available.

Parameters:

function (string) – a Lua string returning a Lua function

LuaFFIPerThreadResponseAction(function)

Invoke a Lua FFI function that accepts a pointer to a dnsdist_ffi_dnsquestion_t object, whose bindings are defined in dnsdist-lua-ffi-interface.h.

The function should return a DNSResponseAction. If the Lua code fails, ServFail is returned.

The function will be invoked in a per-thread Lua state, without access to the global Lua state. All constants (DNSQType, RCode, …) are available in that per-thread context, as well as all FFI functions. Objects and their bindings that are not usable in a FFI context (DNSQuestion, DNSDistProtoBufMessage, PacketCache, …) are not available.

Parameters:

function (string) – a Lua string returning a Lua function

LuaFFIResponseAction(function)

Invoke a Lua FFI function that accepts a pointer to a dnsdist_ffi_dnsquestion_t object, whose bindings are defined in dnsdist-lua-ffi-interface.h.

The function should return a DNSResponseAction. If the Lua code fails, ServFail is returned.

Parameters:

function (string) – the name of a Lua function

LuaResponseAction(function)

Invoke a Lua function that accepts a DNSResponse.

The function should return a DNSResponseAction. If the Lua code fails, ServFail is returned.

Parameters:

function (string) – the name of a Lua function

NegativeAndSOAAction(
    nxd,
    zone,
    ttl,
    mname,
    rname,
    serial,
    refresh,
    retry,
    expire,
    minimum[, options]
)

Turn a question into a response, either a NXDOMAIN or a NODATA one based on ‘’nxd’’, setting the QR bit to 1 and adding a SOA record in the additional section.

Parameters:
  • nxd (bool) – Whether the answer is a NXDOMAIN (true) or a NODATA (false)

  • zone (string) – The owner name for the SOA record

  • ttl (int) – The TTL of the SOA record

  • mname (string) – The mname of the SOA record

  • rname (string) – The rname of the SOA record

  • serial (int) – The value of the serial field in the SOA record

  • refresh (int) – The value of the refresh field in the SOA record

  • retry (int) – The value of the retry field in the SOA record

  • expire (int) – The value of the expire field in the SOA record

  • minimum (int) – The value of the minimum field in the SOA record

  • options (table) – A table with key: value pairs with options

Options:

  • aa: bool - Set the AA bit to this value (true means the bit is set, false means it’s cleared). Default is to clear it.

  • ad: bool - Set the AD bit to this value (true means the bit is set, false means it’s cleared). Default is to clear it.

  • ra: bool - Set the RA bit to this value (true means the bit is set, false means it’s cleared). Default is to copy the value of the RD bit from the incoming query.

  • soaInAuthoritySection: bool - Place the SOA record in the authority section for a complete NXDOMAIN/NODATA response that works as a cacheable negative response, rather than the RPZ-style response with a purely informational SOA in the additional section. Default is false (SOA in additional section).

NoneAction()

Does nothing. Subsequent rules are processed after this action.

PoolAction(poolname[, stop])

Send the packet into the specified pool. If stop is set to false, subsequent rules will be processed after this action.

Parameters:
  • poolname (string) – The name of the pool

  • stop (bool) – Whether to stop processing rules after this action. Default is true, meaning the remaining rules will not be processed.

QPSAction(maxqps)

Drop a packet if it does exceed the maxqps queries per second limits. Letting the subsequent rules apply otherwise.

Parameters:

maxqps (int) – The QPS limit

QPSPoolAction(maxqps, poolname[, stop])

Send the packet into the specified pool only if it does not exceed the maxqps queries per second limits. If stop is set to false, subsequent rules will be processed after this action. Letting the subsequent rules apply otherwise.

Parameters:
  • maxqps (int) – The QPS limit for that pool

  • poolname (string) – The name of the pool

  • stop (bool) – Whether to stop processing rules after this action. Default is true, meaning the remaining rules will not be processed.

RCodeAction(rcode[, options])

Reply immediately by turning the query into a response with the specified rcode. rcode can be specified as an integer or as one of the built-in RCode.

Parameters:
  • rcode (int) – The RCODE to respond with.

  • options (table) – A table with key: value pairs with options.

Options:

  • aa: bool - Set the AA bit to this value (true means the bit is set, false means it’s cleared). Default is to clear it.

  • ad: bool - Set the AD bit to this value (true means the bit is set, false means it’s cleared). Default is to clear it.

  • ra: bool - Set the RA bit to this value (true means the bit is set, false means it’s cleared). Default is to copy the value of the RD bit from the incoming query.

RemoteLogAction(
    remoteLogger[, alterFunction[, options[, metas]]]
)

Changed in version 2.2.0: exportTagsKeyOnly, exportTagsPrefixes and exportTagsStripPrefixes optional keys added to the options table.

Send the content of this query to a remote logger via Protocol Buffer. alterFunction is a callback, receiving a DNSQuestion and a DNSDistProtoBufMessage, that can be used to modify the Protocol Buffer content, for example for anonymization purposes. Since 1.8.0 it is possible to add configurable meta-data fields to the Protocol Buffer message via the metas parameter, which takes a list of name``=``key pairs. For each entry in the list, a new value named name will be added to the message with the value corresponding to the key. Available keys are:

  • doh-header:<HEADER>: the content of the corresponding <HEADER> HTTP header for DoH queries, empty otherwise

  • doh-host: the Host header for DoH queries, empty otherwise

  • doh-path: the HTTP path for DoH queries, empty otherwise

  • doh-query-string: the HTTP query string for DoH queries, empty otherwise

  • doh-scheme: the HTTP scheme for DoH queries, empty otherwise

  • pool: the currently selected pool of servers

  • proxy-protocol-value:<TYPE>: the content of the proxy protocol value of type <TYPE>, if any

  • proxy-protocol-values: the content of all proxy protocol values as a “<type1>:<value1>”, …, “<typeN>:<valueN>” strings

  • b64-content: the base64-encoded DNS payload of the current query

  • sni: the Server Name Indication value for queries received over DoT or DoH. Empty otherwise.

  • tag:<TAG>: the content of the corresponding <TAG> if any

  • tags: the list of all tags, and their values, as a “<key1>:<value1>”, …, “<keyN>:<valueN>” strings. Note that a tag with an empty value will be exported as “<key>”, not “<key>:”.

Subsequent rules are processed after this action.

Parameters:
  • remoteLogger (string) – The remoteLogger object to write to

  • alterFunction (string) – Name of a function to modify the contents of the logs before sending

  • options (table) – A table with key: value pairs.

  • metas (table) – A list of name``=``key pairs, for meta-data to be added to Protocol Buffer message.

Options:

  • serverID="": str - Set the Server Identity field.

  • ipEncryptKey="": str - A key, that can be generated via the makeIPCipherKey() function, to encrypt the IP address of the requestor for anonymization purposes. The encryption is done using ipcrypt for IPv4 and a 128-bit AES ECB operation for IPv6.

  • exportTags="": str - The comma-separated list of keys of internal tags to export into the tags Protocol Buffer field, as “key:value” strings. Note that a tag with an empty value will be exported as “<key>”, not “<key>:”. An empty string means that no internal tag will be exported. The special value * means that all tags will be exported. See Protobuf Logging Reference for some examples.

  • exportTagsKeyOnly=false: boolean - Whether to export tags matched by exportTags or exportTagsPrefixes as key (true) or key:value strings (false, the default).

  • exportTagsPrefixes=""": str - Comma-separated list of prefixes: internal tags whose keys match at least one of these prefixes will be exported into the tags Protocol Buffer field, as key:value strings (or as key if exportTagsKeyOnly is set). Tags whose keys match at least one of the entries in exportTags will be exported as well.

  • exportTagsStripPrefixes=false: boolean - Whether to strip the prefix part of the key when exporting a tag matched by one of the prefixes defined in exportTagsPrefixes.

RemoteLogResponseAction(
    remoteLogger[, alterFunction[, includeCNAME[, options[, metas[, delay]]]]]
)

Changed in version 1.9.0: exportExtendedErrorsToMeta optional key added to the options table.

Changed in version 2.1.0: delay optional parameter added.

Changed in version 2.2.0: exportTagsKeyOnly, exportTagsPrefixes and exportTagsStripPrefixes optional keys added to the options table.

Send the content of this response to a remote logger via Protocol Buffer. alterFunction is the same callback that receiving a DNSResponse and a DNSDistProtoBufMessage, that can be used to modify the Protocol Buffer content, for example for anonymization purposes. includeCNAME indicates whether CNAME records inside the response should be parsed and exported. The default is to only exports A and AAAA records. Since 1.8.0 it is possible to add configurable meta-data fields to the Protocol Buffer message via the metas parameter, which takes a list of name``=``key pairs. See RemoteLogAction() for the list of available keys. Subsequent rules are processed after this action.

Parameters:
  • remoteLogger (string) – The remoteLogger object to write to

  • alterFunction (string) – Name of a function to modify the contents of the logs before sending

  • includeCNAME (bool) – Whether or not to parse and export CNAMEs. Default false

  • options (table) – A table with key: value pairs.

  • metas (table) – A list of name``=``key pairs, for meta-data to be added to Protocol Buffer message.

  • delay (bool) – Delay sending the protobuf until after the DNS response has been sent to the client. Default false.

Options:

  • serverID="": str - Set the Server Identity field.

  • ipEncryptKey="": str - A key, that can be generated via the makeIPCipherKey() function, to encrypt the IP address of the requestor for anonymization purposes. The encryption is done using ipcrypt for IPv4 and a 128-bit AES ECB operation for IPv6.

  • exportTags="": str - The comma-separated list of keys of internal tags to export into the tags Protocol Buffer field, as “key:value” strings. Note that a tag with an empty value will be exported as “<key>”, not “<key>:”. An empty string means that no internal tag will be exported. The special value * means that all tags will be exported. See Protobuf Logging Reference for some examples.

  • exportTagsKeyOnly=false: boolean - Whether to export tags matched by exportTags or exportTagsPrefixes as key (true) or key:value strings (false, the default).

  • exportTagsPrefixes=""": str - Comma-separate list of prefixes:internal tags whose keys match at least of these prefixes will be exported into the tags Protocol Buffer field, as key:value strings (or as key if exportTagsKeyOnly is set). Tags whose keys match at least of the entries in exportTags will be exported as well.

  • exportTagsStripPrefixes=false: boolean - Whether to strip the prefix part of the key when exporting a tag matched by one of the prefixes defined in exportTagsPrefixes.

  • exportExtendedErrorsToMeta="": str - Export Extended DNS Errors present in the DNS response, if any, into the meta Protocol Buffer field using the specified key. The EDE info code will be exported as an integer value, and the EDE extra text, if present, as a string value.

SetAdditionalProxyProtocolValueAction(type, value)

Add a Proxy-Protocol Type-Length value to be sent to the server along with this query. It does not replace any existing value with the same type but adds a new value. Be careful that Proxy Protocol values are sent once at the beginning of the TCP connection for TCP and DoT queries. That means that values received on an incoming TCP connection will be inherited by subsequent queries received over the same incoming TCP connection, if any, but values set to a query will not be inherited by subsequent queries. Subsequent rules are processed after this action.

Parameters:
  • type (int) – The type of the value to send, ranging from 0 to 255 (both included)

  • value (str) – The binary-safe value

SetDisableECSAction()

Disable the addition of EDNS Client Subnet information by dnsdist before passing queries to the backend. This does not remove any existing EDNS Client Subnet value sent by the client, please have a look at SetEDNSOptionAction() instead. Subsequent rules are processed after this action. Note that this function was called DisableECSAction before 1.6.0.

SetDisableValidationAction()

Set the CD bit in the query and let it go through. Subsequent rules are processed after this action. Note that this function was called DisableValidationAction before 1.6.0.

SetECSAction(v4[, v6])

Set the ECS prefix and prefix length sent to backends to an arbitrary value. If both IPv4 and IPv6 masks are supplied the IPv4 one will be used for IPv4 clients and the IPv6 one for IPv6 clients. Otherwise, the first mask is used for both, and can actually be an IPv6 mask. Subsequent rules are processed after this action.

Parameters:
  • v4 (string) – The IPv4 netmask, for example “192.0.2.1/32”

  • v6 (string) – The IPv6 netmask, if any

SetECSOverrideAction(override)

Whether an existing EDNS Client Subnet value should be overridden (true) or not (false). Subsequent rules are processed after this action. Note that this function was called ECSOverrideAction before 1.6.0.

Parameters:

override (bool) – Whether or not to override ECS value

SetECSPrefixLengthAction(v4, v6)

Set the ECS prefix length. Subsequent rules are processed after this action. Note that this function was called ECSPrefixLengthAction before 1.6.0.

Parameters:
  • v4 (int) – The IPv4 netmask length

  • v6 (int) – The IPv6 netmask length

SetEDNSOptionAction(option)

Add arbitrary EDNS option and data to the query. Any existing EDNS content with the same option code will be overwritten. Subsequent rules are processed after this action.

Parameters:
  • option (int) – The EDNS option number

  • data (string) – The EDNS0 option raw content

SetEDNSOptionResponseAction(option)

Added in version 1.9.11.

Add arbitrary EDNS option and data to the response. Any existing EDNS content with the same option code will be replaced. Subsequent rules are processed after this action.

Parameters:
  • option (int) – The EDNS option number

  • data (string) – The EDNS0 option raw content

SetExtendedDNSErrorAction(infoCode[, extraText[, clearExistingEntries]])

Added in version 1.9.0.

Changed in version 2.1.0: clearExistingEntries optional parameter added.

Set an Extended DNS Error status that will be added to the response corresponding to the current query. Subsequent rules are processed after this action.

Parameters:
  • infoCode (int) – The EDNS Extended DNS Error code

  • extraText (string) – The optional EDNS Extended DNS Error extra text

  • clearExistingEntries (bool) – Whether to clear existing EDNS Extended DNS Error codes, default true

SetExtendedDNSErrorResponseAction(infoCode[, extraText[, clearExistingEntries]])

Added in version 1.9.0.

Changed in version 2.1.0: clearExistingEntries optional parameter added.

Set an Extended DNS Error status that will be added to this response. Subsequent rules are processed after this action.

Parameters:
  • infoCode (int) – The EDNS Extended DNS Error code

  • extraText (string) – The optional EDNS Extended DNS Error extra text

  • clearExistingEntries (bool) – Whether to clear existing EDNS Extended DNS Error codes, default true

SetMacAddrAction(option)

Add the source MAC address to the query as EDNS0 option option. This action is currently only supported on Linux. Subsequent rules are processed after this action. Note that this function was called MacAddrAction before 1.6.0.

Parameters:

option (int) – The EDNS0 option number

SetMaxReturnedTTLAction(max)

Cap the TTLs of the response to the given maximum, but only after inserting the response into the packet cache with the initial TTL values.

Parameters:

max (int) – The maximum allowed value

SetMaxReturnedTTLResponseAction(max)

Cap the TTLs of the response to the given maximum, but only after inserting the response into the packet cache with the initial TTL values.

Parameters:

max (int) – The maximum allowed value

SetMaxTTLResponseAction(max)

Cap the TTLs of the response to the given maximum.

Parameters:

max (int) – The maximum allowed value

SetMinTTLResponseAction(min)

Cap the TTLs of the response to the given minimum.

Parameters:

min (int) – The minimum allowed value

SetNoRecurseAction()

Strip RD bit from the question, let it go through. Subsequent rules are processed after this action. Note that this function was called NoRecurseAction before 1.6.0.

SetProxyProtocolValuesAction(values)

Set the Proxy-Protocol Type-Length values to be sent to the server along with this query to values. Subsequent rules are processed after this action.

Parameters:

values (table) – A table of types and values to send, for example: { [0] = foo", [42] = "bar" }

SetReducedTTLResponseAction(percentage)

Reduce the TTL of records in a response to a percentage of the original TTL. For example, passing 50 means that the original TTL will be cut in half. Subsequent rules are processed after this action.

Parameters:

percentage (int) – The percentage to use

SetSkipCacheAction()

Don’t lookup the cache for this query, don’t store the answer. Subsequent rules are processed after this action. Note that this function was called SkipCacheAction before 1.6.0.

SetSkipCacheResponseAction()

Don’t store this answer into the cache. Subsequent rules are processed after this action.

SetTagAction(name, value)

Associate a tag named name with a value of value to this query, that will be passed on to the response. This function will overwrite any existing tag value. Subsequent rules are processed after this action. Note that this function was called TagAction before 1.6.0.

Parameters:
  • name (string) – The name of the tag to set

  • value (string) – The value of the tag

SetTagResponseAction(name, value)

Associate a tag named name with a value of value to this response. This function will overwrite any existing tag value. Subsequent rules are processed after this action. Note that this function was called TagResponseAction before 1.6.0.

Parameters:
  • name (string) – The name of the tag to set

  • value (string) – The value of the tag

SetTempFailureCacheTTLAction(ttl)

Set the cache TTL to use for ServFail and Refused replies. TTL is not applied for successful replies. Subsequent rules are processed after this action. Note that this function was called TempFailureCacheTTLAction before 1.6.0.

Parameters:

ttl (int) – Cache TTL for temporary failure replies

SetTraceAction(value[, options])

Added in version 2.1.0.

Enable or disable OpenTelemetry tracing for this query. Don’t forget to use RemoteLogResponseAction() to actually send the Protobuf with the trace to a collector. Subsequent rules are processed after this action.

Tracing has to be turned on globally as well using setOpenTelemetryTracing().

Parameters:
  • value (bool) – Whether to enable or disable query tracing.

  • options (table) – A table with key=value pairs with options

Options:

  • remoteLoggers: A table of remoteLogger objects to send the traces to. Note that these log messages will be empty, apart from the trace data.

  • useIncomingTraceparent: boolean, default false. Use the information in the TRACEPARENT EDNS option (if any) from the query as the Trace ID and initial Span ID.

  • stripIncomingTraceparent: boolean, default false. Remove the TRACEPARENT EDNS option from the DNS query so it is not passed to the backend server.

  • traceparentOptionCode: integer, default 65500. The EDNS option code for TRACEPARENT EDNS option.

  • sendDownstreamTraceparent: boolean, default false. When true, a TRACEPARENT EDNS option is added to the downstream query with the active Trace ID and the last Span ID of the trace.

SNMPTrapAction([message])

Send an SNMP trap, adding the optional message string as the query description. Subsequent rules are processed after this action.

Parameters:

message (string) – The message to include

SNMPTrapResponseAction([message])

Send an SNMP trap, adding the optional message string as the query description. Subsequent rules are processed after this action.

Parameters:

message (string) – The message to include

SpoofAction(ip[, options])
SpoofAction(ips[, options])

Forge a response with the specified IPv4 (for an A query) or IPv6 (for an AAAA) addresses. If you specify multiple addresses, all that match the query type (A, AAAA or ANY) will get spoofed in.

Note that if you only specify addresses of one type (e.g. only IPv4 addresses), then queries for the other type (in this case AAAA queries), will not be spoofed. If you want to spoof the request for an A record, but not return an IPv6 address on AAAA requests, you could limit this function to A queries and NegativeAndSOAAction() for AAAA queries.

Parameters:
  • ip (string) – An IPv4 and/or IPv6 address to spoof

  • ips ({string}) – A table of IPv4 and/or IPv6 addresses to spoof

  • options (table) – A table with key: value pairs with options.

Options:

  • aa: bool - Set the AA bit to this value (true means the bit is set, false means it’s cleared). Default is to clear it.

  • ad: bool - Set the AD bit to this value (true means the bit is set, false means it’s cleared). Default is to clear it.

  • ra: bool - Set the RA bit to this value (true means the bit is set, false means it’s cleared). Default is to copy the value of the RD bit from the incoming query.

  • ttl: int - The TTL of the record.

SpoofCNAMEAction(cname[, options])

Forge a response with the specified CNAME value.

Parameters:
  • cname (string) – The name to respond with

  • options (table) – A table with key: value pairs with options.

Options:

  • aa: bool - Set the AA bit to this value (true means the bit is set, false means it’s cleared). Default is to clear it.

  • ad: bool - Set the AD bit to this value (true means the bit is set, false means it’s cleared). Default is to clear it.

  • ra: bool - Set the RA bit to this value (true means the bit is set, false means it’s cleared). Default is to copy the value of the RD bit from the incoming query.

  • ttl: int - The TTL of the record.

SpoofRawAction(rawAnswer[, options])
SpoofRawAction(rawAnswers[, options])

Changed in version 1.9.0: Added the optional parameter typeForAny.

Forge a response with the specified raw bytes as record data.

-- select queries for the 'raw.powerdns.com.' name and TXT type, and answer with both a "aaa" "bbbb" and "ccc" TXT record:
addAction(AndRule({QNameRule('raw.powerdns.com.'), QTypeRule(DNSQType.TXT)}), SpoofRawAction({"\003aaa\004bbbb", "\003ccc"}))
-- select queries for the 'raw-srv.powerdns.com.' name and SRV type, and answer with a '0 0 65535 srv.powerdns.com.' SRV record, setting the AA bit to 1 and the TTL to 3600s
addAction(AndRule({QNameRule('raw-srv.powerdns.com.'), QTypeRule(DNSQType.SRV)}), SpoofRawAction("\000\000\000\000\255\255\003srv\008powerdns\003com\000", { aa=true, ttl=3600 }))
-- select reverse queries for '127.0.0.1' and answer with 'localhost'
addAction(AndRule({QNameRule('1.0.0.127.in-addr.arpa.'), QTypeRule(DNSQType.PTR)}), SpoofRawAction("\009localhost\000"))
-- rfc8482: Providing Minimal-Sized Responses to DNS Queries That Have QTYPE=ANY via HINFO of value "rfc8482"
addAction(QTypeRule(DNSQType.ANY), SpoofRawAction("\007rfc\056\052\056\050\000", { typeForAny=DNSQType.HINFO }))

DNSName:toDNSString is convenient for converting names to wire format for passing to SpoofRawAction.

sdig dumpluaraw and pdnsutil raw-lua-from-content from PowerDNS can generate raw answers for you:

$ pdnsutil raw-lua-from-content SRV '0 0 65535 srv.powerdns.com.'
"\000\000\000\000\255\255\003srv\008powerdns\003com\000"
$ sdig 127.0.0.1 53 open-xchange.com MX recurse dumpluaraw
Reply to question for qname='open-xchange.com.', qtype=MX
Rcode: 0 (No Error), RD: 1, QR: 1, TC: 0, AA: 0, opcode: 0
0 open-xchange.com. IN  MX  "\000c\004mx\049\049\012open\045xchange\003com\000"
0 open-xchange.com. IN  MX  "\000\010\003mx\049\012open\045xchange\003com\000"
0 open-xchange.com. IN  MX  "\000\020\003mx\050\012open\045xchange\003com\000"
Parameters:
  • rawAnswer (string) – The raw record data

  • rawAnswers ({string}) – A table of raw record data to spoof

  • options (table) – A table with key: value pairs with options.

Options:

  • aa: bool - Set the AA bit to this value (true means the bit is set, false means it’s cleared). Default is to clear it.

  • ad: bool - Set the AD bit to this value (true means the bit is set, false means it’s cleared). Default is to clear it.

  • ra: bool - Set the RA bit to this value (true means the bit is set, false means it’s cleared). Default is to copy the value of the RD bit from the incoming query.

  • ttl: int - The TTL of the record.

  • typeForAny: int - The record type to use when responding to queries of type ANY, as using ANY for the type of the response record would not make sense.

SpoofSVCAction(svcParams[, options])

Forge a response with the specified SVC record data. If the list contains more than one SVCRecordParameters (generated via newSVCRecordParameters()) object, they are all returned, and should have different priorities. The hints provided in the SVC parameters, if any, will also be added as A/AAAA records in the additional section, using the target name present in the parameters as owner name if it’s not empty (root) and the qname instead.

Parameters:
  • svcParams (table) – List of SVCRecordParameters from which to generate the record data to return

  • options (table) – A table with key: value pairs with options.

Options:

  • aa: bool - Set the AA bit to this value (true means the bit is set, false means it’s cleared). Default is to clear it.

  • ad: bool - Set the AD bit to this value (true means the bit is set, false means it’s cleared). Default is to clear it.

  • ra: bool - Set the RA bit to this value (true means the bit is set, false means it’s cleared). Default is to copy the value of the RD bit from the incoming query.

  • ttl: int - The TTL of the record.

SpoofPacketAction(rawPacket, len)

Spoof a raw self-generated answer

Parameters:
  • rawPacket (string) – The raw wire-ready DNS answer

  • len (int) – The length of the packet

TCAction()

Create answer to query with the TC bit set, and the RA bit set to the value of RD in the query, to force the client to TCP. Before 1.7.0 this action was performed even when the query had been received over TCP, which required the use of TCPRule() to prevent the TC bit from being set over TCP transports.

TCResponseAction()

Added in version 1.9.0.

Truncate an existing answer, to force the client to TCP. Only applied to answers that will be sent to the client over TCP. In addition to the TC bit being set, all records are removed from the answer, authority and additional sections.

TeeAction(remote[, addECS[, local[, addProxyProtocol]]])

Changed in version 1.9.0: Added the optional parameter addProxyProtocol.

Send copy of query to remote, keep stats on responses. If addECS is set to true, EDNS Client Subnet information will be added to the query. If addProxyProtocol is set to true, a Proxy Protocol v2 payload will be prepended in front of the query. The payload will contain the protocol that delivered the initial query (UDP or TCP), as well as the initial source and destination addresses and ports. If local has provided a value like “192.0.2.53”, dnsdist will try binding that address as local address when sending the queries. Subsequent rules are processed after this action.

Parameters:
  • remote (string) – An IP:PORT combination to send the copied queries to

  • addECS (bool) – Whether to add ECS information. Default false.

  • local (str) – The local address to use to send queries. The default is to let the kernel pick one.

  • addProxyProtocol (bool) – Whether to prepend a proxy protocol v2 payload in front of the query. Default to false.

UnsetTagAction(name)

Added in version 2.1.0.

Remove a tag named name. Subsequent rules are processed after this action.

Parameters:

name (string) – The name of the tag to unset

UnsetTagResponseAction(name)

Added in version 2.1.0.

Remove a tag named name. Subsequent rules are processed after this action.

Parameters:

name (string) – The name of the tag to unset