YourAmigo lookup and forward irule
Having issues with new F5's lookup forwarding YourAmigo.com. Have a ticket opened with F5 and the engineer provided the following solution from DevCentral https://devcentral.f5.com/community/group/asg/50/aft/27982/showtab/groupforums. Still getting TCL error.
Rewrite HTTP Host header
HTTP::header replace Host "blah.youramigo.com"
Hold HTTP and perform DNS lookup
NAME::lookup blah.youramigo.com
HTTP::collect
}
when NAME_RESOLVED {
log local0. "Forwarding to YourAmigo at [NAME::response address 0]"
node [NAME::response address 0] 80
HTTP::release
node 69.36.35.147 80
Mon Mar 18 14:11:57 GMT 2013 err tmm tmm[7845] 01220001 TCL error: /Common/YourAmigo-Baby_offsite_logger - while executing "NAME::response address 0"
Mon Mar 18 14:11:57 GMT 2013 info tmm tmm[7845] Rule /Common/YourAmigo-Baby_offsite_logger : Forwarding to YourAmigo at
cat /var/named/config/named.conf
restrict rndc access to local machines
use the key in the default place: /config/rndc.key
controls { inet 127.0.0.1 port 953 allow { 127.0.0.1 ;}; };
logging {
channel logfile {
syslog daemon;
severity error;
print-category yes;
print-severity yes;
print-time yes;
};
category default {
logfile;
};
category config {
logfile;
};
category notify {
logfile;
};
};
options {
listen-on port 53 { 127.0.0.1; };
listen-on-v6 port 53 { ::1; };
set this to yes when you want to resolve off
box. setting it to yes when you dont actuallly
have a bind server configured will result in
bind timeouts for many commmands
recursion yes;
forward only;
directory "/config/namedb";
allow-transfer {
localhost;
};
check-names master warn;
change to "no" if you want to be able to add
MX records that do not reference a record that has an A record
check-integrity yes;
max-journal-size 1M;
forwarders {209.x.x.x; 209.x.x.x; };
};
acl "zrd-acl-000-000" {
127.10.0.0;
};
acl "local-loopback-clients" {
127.0.0.0/8;
};
view "internal" {
match-clients { "local-loopback-clients"; };
recursion yes;
};
view "external" {
match-clients { "zrd-acl-000-000"; any; };
};
server 209.x.x.x {
};
server 209.x.x.x {
};