Bug ID 898201: Fqdn nodes are not getting populated after BIG-IP reboot when DNS server is accessed through a local virtual server.

Last Modified: Apr 01, 2021

Bug Tracker

Affected Product:  See more info
BIG-IP TMOS(all modules)

Known Affected Versions:
12.1.0, 12.1.0 HF1, 12.1.0 HF2, 12.1.1, 12.1.1 HF1, 12.1.1 HF2, 12.1.2, 12.1.2 HF1, 12.1.2 HF2, 12.1.3,,,,,,,, 12.1.4,, 12.1.5,,,, 13.1.0,,,,,,,,, 13.1.1,,,,, 13.1.3,,,,,,, 14.0.0,,,,,, 14.0.1,, 14.1.0,,,,,, 14.1.2,,,,,,,,, 14.1.3,, 14.1.4,, 15.0.0, 15.0.1,,,,, 15.1.0,,,,,, 15.1.1, 15.1.2,, 16.0.0,, 16.0.1,

Opened: Apr 11, 2020
Severity: 4-Minor


After reboot, no access to services host using fqdn nodes. -- fqdn nodes are not populated with IP addresses. -- Unable to access virtual servers served by pools using fqdn nodes.


-- FQDN DNS requests bypassing the listening virtual server. -- Unable to access the pools of those configured fqdn nodes.


The issue happens after the BIG-IP is rebooted. -- when DNS server is accessed through a local virtual server. -- Single arm cloud BIG-IP with virtual server listening for DNS requests to redirect.


-- restarting dynconfd. -- Running a script to trigger off "Tmm ready" and either delete the bad flow(s) or a specific connflow entry. -- change the dummy dns server to be something in the same subnet as the single interface.

Fix Information


Behavior Change