For more information regarding the security incident at F5, the actions we are taking to address it, and our ongoing efforts to protect our customers, click here.

Forum Discussion

Ethan_Erchinger's avatar
Ethan_Erchinger
Icon for Nimbostratus rankNimbostratus
Mar 09, 2006

Snat pool choice based on destination URL

Hi,     We have a group of servers that make outbound HTTP requests to a partner. We'd like requests going to a specific uri, call it partner.com/a to come from a specific pool of addresses. R...
application delivery
dev
devops
iRules
Ethan_Erchinger's avatar
Ethan_Erchinger
Icon for Nimbostratus rankNimbostratus
Mar 12, 2006
Sorry, I thought I had used the proper formatting. Honestly the "template" is a little skimpy on details..but whatever.

I have a little update on a problem we ran into with DNS lookup, I'll update the codeshare as well, but thought I'd complete the thread for completeness.

While DNS lookup does work as described in the below article, it only works correctly when the DNS lookup returns 1 IP.

http://devcentral.f5.com/Default.aspx?tabid=28&forumid=5&postid=6546&view=topic

To get around this limitation we found this to work nicely.


 when NAME_RESOLVED {
   set ::node [lindex [split [NAME::response] " "] 0]
   node $::node 80
 }

This will take the first response from the DNS server and set the "node" variable to that IP. Otherwise $::node will be set to multiple IPs, and subsequent requests to that node will fail.