Forum Discussion
PhillyPDXMike
Nov 03, 2020Altocumulus
What is the syntax equivalentof RESOLV::lookup with the RESOLVER::name_lookup command?
With RESOLV::lookup being deprecated as of version 15.1 in favor of the RESOLVER and DNSMSG namespaces, I am not finding detailed enough documentation and examples to convert my 14.1 iRule to the new...
PeteWhite
Nov 09, 2020Employee
So this is a more object-orientated and scalable way of doing lookups - you can think of the response ($result) being a data object which you can then interrogate as you want to. Below is an example,
when CLIENT_ACCEPTED {
set result [RESOLVER::name_lookup "/Common/resolver1" [IP::client_addr PTR]
log local0.debug "Response code: [ DNSMSG::header $result rcode ]"
foreach rr { [RESOLVER::summarize $result] } {
log local0.debug "Response from resolver1 for [IP::client_addr]: $rr"
}
}
Recent Discussions
Related Content
DevCentral Quicklinks
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com
Discover DevCentral Connects