Forum Discussion
Link controller and Traffic Forwarding (DNS)
hi guys, hope you can help as usual.
I'm deploying a Link controller but I want it to only reoslve WIDE IP configured and let already existing DNS to handle other requests.For example, say we have one domain.com running in the site and there's a WIP:app01.domain.com. I need the bigip to resolve only app01.domain.com but www.domain,com (an other different than the one in the WIP). for those exlcuded cases I need the LC to let the other DNS to work that.
Looking for information on ASKF5 i found that I can configure the LC in brdige mode:
http://support.f5.com/kb/en-us/prod...-05-1.html
so that it can forward DNS request to other resources. Here's where I'm little confused because it states that I need to create a listener using the IP address of DNS server. Do i have to change the IP of the DNS to other because the BIG-IP is using it? or Have I need to create a pool with the DNS within an associate it to the Virtual Server automatically created when you add a listener (the one with no monitor)?
i'm testing this in a lab enviroment.
So confused.
Thanks in advanced
HHeredia
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