Forum Discussion
RESOLV::lookup limitations
Hi all,
I use the RESOLV::lookup command in an iRule and I've got a little problem.
It seems that the number of answer is limited to 16.
Then I've two questions :
1) is it true ?
2 how can i bypass this limitation ?
Thanks for your help
Lionel
Her is my iRule :
when DNS_REQUEST timing on {
if { ([DNS::question type] eq "A")} {
if { [class match [getfield [DNS::question name] ".mnc999.mcc999.gprs" 1] starts_with cls_sgsn]} {
if { [LB::status node 10.64.2.212 ] eq "up" } {
set static::dnrl 10.64.2.212
} else {
set static::dnrl 10.62.2.212
}
set resultats [RESOLV::lookup @$static::dnrl -a "[getfield [DNS::question name] ".mnc999.mcc999.gprs" 1].mnc000f.mcc000f.gprs"]
foreach resultat $resultats {
DNS::answer insert "[DNS::question name]. 3600 IN A ${resultat}"
}
DNS::return
}
}
}
3 Replies
- hoolio
Cirrostratus
Hi,
I did a quick search for the max response count TMM would support but couldn't find anything. Could you open a case on this and reply back with what you get?
Thanks, Aaron
- Lionel_Saccoman
Nimbostratus
Hi, Thanks Aaron. I opend a case. I havn't answer at this time. I'll keep you in touch. Lionel
- Lionel_Saccoman
Nimbostratus
Hi this limitation is hard coded ....
Help guide the future of your DevCentral Community!
What tools do you use to collaborate? (1min - anonymous)Recent Discussions
Related Content
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com