Forum Discussion

Mate_132781's avatar
Mate_132781
Icon for Cirrostratus rankCirrostratus
Apr 11, 2016

iRule DNS resolving, reCaptcha and CMP Hash

Hi,

 

we are using some iRules for reCaptcha. iRule is using DNS resolving to DNS server 8.8.4.4 and everything is working fine.

 

On same platform we are using bandwidth control and we need to change CMP hash on outside (Internet facing) VLAN from Default do Source address.

 

After CMP Hash algorithm change, reCaptcha not working. Looks like F5 can't resolve IP address of www.google.com.

 

F5 has configured DNS servers and in nslookup resolving is working (even CMP hash is changed), but in this case F5 is using DNS server configured in iRule.

 

More strange thing is that there is nothing in TCPDUMP, like it not eve trying to resolve IP.

 

After we changed CMP hash to default, everything is working fine.

 

We tried to reboot device, but situation is the same. Things are also happening on second device (not in cluster, just on other site).

 

Have anybody any idea?

 

  • Amy_123193's avatar
    Amy_123193
    Historic F5 Account

    This is a known issue documented in SOL17357.

     

    This is fixed in v12.0 and is slated to be fixed in TMOS v11.6.1 when it is released, however if you need a fix for adifferent version you may request an engineering hotfix through F5 Support.

     

    • Mate_132781's avatar
      Mate_132781
      Icon for Cirrostratus rankCirrostratus
      Tnx for help. We have TMOS 11.6 HF6 and we already opened case. We'll wait to official support answer and we'll start with upgrade preparation to TMOS 12.0 version.
  • This is a known issue documented in SOL17357.

     

    This is fixed in v12.0 and is slated to be fixed in TMOS v11.6.1 when it is released, however if you need a fix for adifferent version you may request an engineering hotfix through F5 Support.

     

    • Mate_132781's avatar
      Mate_132781
      Icon for Cirrostratus rankCirrostratus
      Tnx for help. We have TMOS 11.6 HF6 and we already opened case. We'll wait to official support answer and we'll start with upgrade preparation to TMOS 12.0 version.