I have a legacy ACP rule on an FMC managed FTD with an FQDN as the destination. The FQDN no longer exists but the FTD is continually trying to resolve the hostname. I've disabled the rule (not deleted it) but the FTD continues to try and resolve the hostname.
I've recreated the rule on an FTDv in the lab and I'm seeing the same behaviour. I've deleted the rule in the ACP and deployed it. I can see the rule and the FQDN object have been removed from the FTD configuration; however, the FTD is continuing to try and resolve the hostname. It has taken a reboot of the FTD for the behaviour to stop.
Is this expected behaviour. The name servers for the domain the host is in exist but refuse connections if that makes a difference. The live FMC/FTD is 7.2 and the lab kit is all shiny 7.7.10.
