Forum Discussion

Jason_Keating's avatar
Jason_Keating
Icon for Altostratus rankAltostratus
Sep 06, 2010

RESOLV::lookup ptr fail

Hi,

 

 

Firstly I'm running 10.2.0 1755.1

 

 

Hoping someone can help me here, I want to use RESOLV::lookup to do reverse lookups on addresses for some logging.

 

 

My problem is I get no result from a lookup on an address, I do get a result from a lookup on a FQDN.

 

 

I have a DNS Server configured, nslookup, host and dig all work great.

 

 

I've also tried NAME:lookup, this also fails.

 

 

Querying A records seems to work fne, but PTR dont work. I've run tcpdump while executing my iRule, and I see the PTR query go out - and I see a response! (also happens to be identical traffic to when I do a manual nslookup) ... but still no output from RESOLV::lookup (or NAME::lookup for that matter)

 

 

I've searched ask.f5 and the forum, I found the references below.....neither of them help unfortunetly (tried turning on recursive and the tmm_base config is now 'out-of'the-box' with 10....

 

 

http://devcentral.f5.com/Wiki/defau...ngDNS.html

 

http://devcentral.f5.com/Community/...fault.aspx

 

 

Here is an iRule I've been using to test...

 

 

when CLIENT_ACCEPTED {

 

set client_addr [IP::client_addr]

 

log local0. "$client_addr"

 

log local0. "[RESOLV::lookup @10.163.134.22 [IP::client_addr]]"

 

log local0. "[RESOLV::lookup @10.163.134.22 -ptr [IP::client_addr]]"

 

log local0. "[RESOLV::lookup @10.163.134.22 -ptr "10.178.78.165"]"

 

log local0. "[RESOLV::lookup @10.163.134.22 -ptr 10.178.78.165]"

 

log local0. "[RESOLV::lookup @10.163.134.22 10.178.78.165]"

 

log local0. "[RESOLV::lookup @10.163.134.22 "host.domain.com"]"

 

}

 

 

The only result I get is from the last line ...

 

 

Has anyone struck this?

 

 

Thanks

 

J

2 Replies

  • Hi J,

     

     

    I've only done basic testing of the RESOLV:: commands. If you're not seeing the expected results and haven't gotten a response yet, you could try opening a case with F5 Support. If you have already or end up doing this, could you post back any info you get?

     

     

    Thanks, Aaron
  • Hi Jason,

     

     

    I see you opened a case on the error and received a bug ID of 340659. I updated the RESOLV::lookup wiki page to note this ID.

     

     

    Aaron