NAME_RESOLVED¶

Description¶

This event is triggered after a NAME__lookup command has been issued and a response has been received. This response could be either a success or a failure.

Warning

This command has been deprecated with the release of version 15.1 in favor of the RESOLVER and DNSMSG namespaces.

Examples¶

when HTTP_REQUEST {
  NAME::lookup [HTTP::host]
}

when NAME_RESOLVED {
  node [NAME::response] 80
}

Related Information¶

Available Commands:

clone - Causes the system to clone traffic to the specified pool or pool member regardless of monitor status.
forward - Sets the connection to forward IP packets.
HTTP::redirect - Redirects an HTTP request or response to the specified URL.
HTTP::release - Releases the data collected via HTTP::collect.
HTTP::respond - Generates a response to the client as if it came from the server.
IP::idle_timeout - Returns or sets the idle timeout value.
ip_ttl - Returns the TTL of the latest IP packet received.
lasthop - Sets the lasthop of an IP connection.
listen - Sets up a related ephemeral listener to allow an incoming related connection to be established.
NAME::response - Returns a list of records received in response to a DNS query
nexthop - Sets the nexthop of an IP connection.
node - Sends the packet directly to the identified server node.
peer - Causes the specified iRule commands to be evaluated under the peer’s (opposite) context.
persist - Causes the system to use the named persistence type to persist the connection.
pool - Causes the system to load balance traffic to the specified pool or pool member regardless of monitor status.
session - Utilizes the persistence table to store arbitrary information based on the same keys as persistence.

Sample Code:

Block requests by reverse DNS record - Performs a reverse DNS lookup to validate client IP
Destination Snat Using DNS - This iRule. selects a snatpool based on which virtual called the iRule. and will select the member servers to use based on DNS resolution.

Introduced: BIGIP-9.0.0
Deprecated: BIGIP-15.1.0

The BIG-IP API Reference documentation contains community-contributed content. F5 does not monitor or control community code contributions. We make no guarantees or warranties regarding the available code, and it may contain errors, defects, bugs, inaccuracies, or security vulnerabilities. Your access to and use of any code available in the BIG-IP API reference guides is solely at your own risk.