For more information regarding the security incident at F5, the actions we are taking to address it, and our ongoing efforts to protect our customers, click here.

Use Fully Qualified Domain Name (FQDN) for GSLB Pool Member with F5 DNS

Normally, we define a specific IP (and port) to be used as GSLB pool member. This article provides a custom configuration to be able to use Fully Qualified Domain Name (FQDN) as GSLB pool member--wit...
Published Sep 30, 2024
Version 1.0
application delivery
BIG-IP
f5 dns
gslb
GSLBPOOL
gtm
GTM DNS
MichaelOLeary's avatar
MichaelOLeary
Icon for Employee rankEmployee
Nov 23, 2024

Hi Doddy_ZUHRI ,

I have followed your article and set this up and it works fine. Thanks for documenting. It's a clever workaround. 

My only feedback is the script used in the EAV monitor has this variable which is not defined: $MONITOR_NAME, but it does not break the script. The name of the pid file is just not what you might expect.

When I first set this up in a lab, I forgot that each instance of BIG-IP DNS must have itself as a server, or another BIG-IP instance, in order to be a Prober. So in my lab I had everything set up correctly except only 1 Generic Host and no BIG-IP instance. The DataCenter was therefore blue and the EAV monitor was not firing. I was focused on finding an issue inside the script, but it was my lack of a GSLB server of type BIG-IP that was the problem. Perhaps this could help someone else.

Hopefully this helps others and I'm happy for folks to reach out to me directly over DevCentral messaging if they want me to walk them through this. Thanks again Doddy.

Mike.