F5 Big IP Edge Client - DNS Name lookup failure

AVG Protection
6

Hello Darryl,

We're glad to look into this & help you.
Regrettably, an update of AVG Internet Security cannot be rolled back.
In this case, let's temporarily disable the individual shields/components of your AVG Internet Security & narrow down the shield/component that's causing this issue.
Refer to this article to temporarily disable the individual shields/components of your AVG Internet Security.
Keep us updated.

2

Hello Darryl,

We're glad to look into this & help you.
Regrettably, an update of AVG Internet Security cannot be rolled back.
In this case, let's temporarily disable the individual shields/components of your AVG Internet Security & narrow down the shield/component that's causing this issue.
Refer to this article to temporarily disable the individual shields/components of your AVG Internet Security.
Keep us updated.

1

Hi,
I use the F5 Big IP Edge Client daily to connect remotely to my work network.  As usual, I connected fine earlier today, but all of a sudden I am getting DNS Name Lookup failures when I try to connect to servers on my work network.

I've looked in the AVG logs and the only entries for 'Apps blocked' show…
F5 Networks DNS Relay Proxy for Windows (C:\Windows\SysWOW64\F5FltSRv.exe)
Blocked by Rule: Public Tcp/Udp In Block
There are multiple entries the same as this, each a few seconds apart, with the latest entry corresponding to the time when the issue emerged.

I have tried extensively to troubleshoot over the last couple of hours without success.  Their have been no further Log entries since the one corresponding to the time when the issue emerged.

I'm at a loss to how to address this issue – can you offer any advice please?

Regards
Darryl

3

Thank you for narrowing down the issue, Darryl.
We appreciate your efforts in resolving this issue.
We would like to inform you that this issue might have happened due to a recent update. We suggest you to add the website to AVG exception list and check if it works.
You can refer to this article: https://bit.ly/3DBiY6J to know more about AVG Fake Website shield.
Thank you and please keep us updated.

5

Thank you Sreenu,

Yes, it seems the issue arose with a recent update.

I already had exceptions specified for http:// and https://, bit not for dns://.  Adding further exceptions in the form dns://.example.net as advised in the article: How to use Fake Website Shield in AVG Internet Security | AVG has resolved my issue.

Thanks for the prompt help.

Kind regards
Darryl

4

Thank you Midhun,

I stepped through each of the shields one-by-one.  I have identified that it is the Fake Website Shield that is causing the issue.  WIth Fake Website Sheild turned off, I have no problem connecting to my work servers – as soon as I turn Fake Website Sheild back on, the problem is again present.
 
Can you advise how I proceed to workaround this issue please?  Or is a patch from AVG required?

Kind regards
Darryl