Forum Discussion
Marvin
Mar 20, 2019Cirrocumulus
I found out the the DNSresolver object was configured in route domain 0, as we use route domains and strictly isolated we received that error message. I changed the DNSresolver object to the right route domain and the error disappeared, however I now see timeout issue. In tcpdump I see still that the F5 self IP is trying to reach public DNS servers, but it should resolve using the DNS servers configured on the F5 system via management interface, however this is not happening.
So the issue you are experience most probably has to to with the same DNS connectivity issue, perhaps you also use route domains in your setup?