cancel
Showing results for 
Search instead for 
Did you mean: 

BIG-IP DNS Resolution to actual server IP

Jacob_Klein
Nimbostratus
Nimbostratus

I am using BIG-IP DNS for geographic based IP resolution of my proxy servers. If the DNS request comes from Site A, BIG-IP responds with the IP for proxy 1 ; Site B resolves to proxy 2 using Topology Records. This is the easy part.

 

I am NOT wanting client traffic between the users and the proxy to actually go through the BIG-IP. I am only wanting BIG-IP to effectively act as an intelligent DNS server. If the proxy server IP is actually 192.168.100.57, then that is what I need the BIG-IP to resolve to.

 

I tried using LTM Virtual Servers with the IP of the VS matching the IP of the Pool Member, i.e. the proxy server. Unfortunately, this caused issues where the Health Monitor would suddenly fail until it was removed and re-added to the LTM Pool.

 

I am currently running the Health Monitor in the DNS module and it seems to be working, however, I am needing to move the functionality to another vCMP but the same configuration is failing.

2 REPLIES 2

Simon_Blakely
F5 Employee
F5 Employee

It sounds like you are somewhat confused about the nature of BigIP DNS and how to configure it.

 

BigIP DNS just resolves DNS names to IP addresses - the client then connects directly to the returned IP address, and if that IP address is not a BigIP LTM virtual server IP, then traffic will not pass through the BigIP.

 

You just need to define your Proxy IPs as Generic Server objects, not BigIP Virtual Servers.

Jacob_Klein
Nimbostratus
Nimbostratus

No, not confused.

 

I have them defined as Generic Servers, however, the Health Monitors were failing.

 

A friend suggested creating a Prober Pool. Once done, everything started passing the monitor.

 

Thanks for your input though.