Forum Discussion
BigIP GTM/DNS - no listener?
I recently ran an ihealth report on one of our BigIP GTM servers in preparation for an upgrade from V11.x to 13. One of the warnings received was that "The BIG-IP GTM configuration is missing a listener object". I checked and indeed there are no listeners defined. That being said, the system is working correctly - and has been for a couple of years. The GTM (and its identical twin at another DC) is authoritative for several of our zones. It serves a mix of static IPs configured through ZoneRunner and WideIPs. There are no other (non-F5) DNS servers in the mix.
I've read through (many) articles and documentation on configuring listeners and just can't see what I'm missing.
Do I, in fact, need to add a listener to this device which is currently behaving as expected? If so, what is its purpose?
Thanks
- Mohammed_M_IrfaNimbostratus
Hello,
Can you please share the file location or path and file name?
options { listen-on port 53 { 127.0.0.1; "zrd-acl-000-000"; }; listen-on-v6 port 53 { ::1; };
- Mohammed_M_IrfaNimbostratus
Thanks Stanislas
- Mohammed_M_IrfaNimbostratus
Thanks Guys!! i got the location of file "named.conf".
- Stanislas_Piro2Cumulonimbus
You can edit it in webui. Don’t edit configuration files!
- Mohammed_M_Irf1Nimbostratus
Hello,
Can you please share the file location or path and file name?
options { listen-on port 53 { 127.0.0.1; "zrd-acl-000-000"; }; listen-on-v6 port 53 { ::1; };
- Mohammed_M_Irf1Nimbostratus
Thanks Stanislas
- Mohammed_M_Irf1Nimbostratus
Thanks Guys!! i got the location of file "named.conf".
- Stanislas_Piro2Cumulonimbus
You can edit it in webui. Don’t edit configuration files!
- Stanislas_Piro2Cumulonimbus
May be the Bind server is responding to any DNS request instead of GTM.
to make it work, the Bind option
may have been changed.listen-on port 53 { 127.0.0.1; };
GTM, like all others BigIP products requires a "listener" object to handle traffic.
This listener object is a Virtual server with specific properties.
A GTM listener create a Virtual server listening on port 53 (tcp or udp) with a dns profile.
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