NimbostratusI use RESOLV::lookup to perform a DNS query, but RESOLV::lookup don't work. It returns blank for a hostname.Why? My irules: when HTTP_REQUEST { log local0.info "www.f5.com is currently at IP [RESOLV::lookup @218.2.135.1 -a "www.f5.com"]" }
218.2.135.1 is a DNS server IP address.
Nimbostratus
EmployeeHi,
I suppose you forget to set a default root on the TMOS (to reach your DNS server). Management route can not be used. Set a default root in Network > Routes.
Just made a test in my lab, and without any route, no DNS request.
Regards Matt
NimbostratusHi, I have set a default root on the TMOS (to reach my DNS server). When the management interface is down, I ping my DNS server on the command line,the DNS server is reachable.I use nslookup to resolve the domain "www.f5.com" on the command line,it is successful.But RESOLV::lookup don't work. Then I create a volume and install 12.0.0 software,then switch default boot volume to the volume. RESOLV::lookup can work on 12.0.0 software version.I don't do any other settings.Why? I think whether it is a bug of 11.6.0 software.
NimbostratusHi, Was this issue fixed? We do see a similar issue in our environment running 11.5.3 version. Thanks
NimbostratusIt is a bug. When I upgrade 11.6.0 version to 12.0.0 version, I fix this issue. I think you can try to upgrade your environment from 11.5.3 version to 12.0.0 version.
NimbostratusThanks Peter for your help. I will check on this on our environment.
CirrusThanks Peter for your help. I will check on this on our environment.
CirrusHi, Was this issue fixed? We do see a similar issue in our environment running 11.5.3 version. Thanks
NimbostratusHi Aditya,
Are the upgrade changes made by you resolve the RESOLV::lookup as well?
Thanks
CirrusHi Muhammad,
We made a few changes in the iapp in respect to resolv which fixed the issue in 11.5.3 itself.
These articles may help.
https://support.f5.com/csp/article/K14320
https://support.f5.com/csp/article/K12398
Regards,
Aditya
NimbostratusHi Muhammad,
We made a few changes in the iapp in respect to resolv which fixed the issue in 11.5.3 itself.
These articles may help.
https://support.f5.com/csp/article/K14320
https://support.f5.com/csp/article/K12398
Regards,
Aditya