Forum Discussion
f5user_108265
Nimbostratus
Jul 18, 2008GTM iRule defining external DNS server
Hi everybody,
I am facing the following problem. I would like to force the GTM to query an internal (accessible only by the BIG-IP on the private side) DNS server if the DNS record cannot be found on the GTM/ZoneRunner level.
Imagine the following: GTM is managing the company.com domain. There are 4 wide IPs defined within it: a.company.com, b.company.com, c.company.com and d.company.com. Currently, if a DNS query for e.company.com arrives, GTM will respond with an answer saying that it failed to resolve the name. However, what I would like to do is to configure GTM so that before it sends the failed message, it will forward the DNS query to the internal DNS server for resolution. IF the server is aware of the e.company.com record it should send it back to GTM and eventually the client. Otherwise, GTM should respond that it could not resolve the name.
Is this do-able on the BIG-IP and GTM Wide IP rules? If so, could you tell me how to achieve this? My understanding is that it would require one to enable the recursion on the BIG-IP, as well as define iRule with the use of "when LB_FAILED". Am I right?
Thanks,
ALeu
8 Replies
- JRahm
Admin
Yes, you would enable recursion (beware, note the CERT VU800113 published a couple of weeks ago) and set up forwarders in your bind configuration (GTM->ZoneRunner->Named Configuration)options { forward only; forwarders { ns1.internal.company.com; ns2.internal.company.com; }; recursion yes; };
- ALeu_26892
Nimbostratus
Posted By citizen_elah on 07/21/2008 5:42 AM
options { forward only; forwarders { ns1.internal.company.com; ns2.internal.company.com; }; recursion yes; };
type forward; forwarders { internal.dns.server1.com; internal.dns.server2.com; };
recursion yes;
- JRahm
Admin
The forwarders in the named options section are your name servers, not the zones. You can forward by zone instead of globally. This must be setup in each zone's configuration:zone "internal.company.com" in { type forward; masters {ns1.internal.company.com; ns2.internal.company.com}; };
- ALeu_26892
Nimbostratus
Posted By citizen_elah on 07/21/2008 6:51 AM
- JRahm
Admin
In your case, enable recursion in the options secution and just create the zones you want to foward as shown below:options { recursion yes; }; zone "company.com" { type forward; forwarders { y.y.y.y; }; forward only; };
- JRahm
Admin
I guess I should ask if the clients in this case are desktops or other name servers. If other name servers, recursion can be disabled. - ALeu_26892
Nimbostratus
Posted By citizen_elah on 07/21/2008 8:00 AM
- JRahm
Admin
I noticed that behavior in 9.2.3, but it works fine in versions 9.2.4 and 9.4.3.
Recent Discussions
Related Content
DevCentral Quicklinks
* 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
Discover DevCentral Connects