Suspicious DNS Query's

Showing results for 
Show  only  | Search instead for 
Did you mean: 
Please sign in to see details of an important advisory in our Customer Advisories area.

Suspicious DNS Query's

L1 Bithead


We are running version 5.0.6 for a few weeks now and looks very good.

We see now also in our threat detection the following threat "Suspicious DNS Query : ......" and this is blocked.

This is very cool to block at dns level spyware and malware but the disadvantage of this is that the source client ip address is always your DNS server.

So you need to look in to your logs of your DNS Server to find out the infected client.

But if you have a distributed DNS infrastructure and many DNS Servers spread over several location in Europe then this a hard job to do.

Why is it not possible to redirect Suspicious DNS Query's to a honeypot IP address so you can then detect the real client's ip address?

Maybe a future request!!

Or does someone have a better idea how to deal with this issue?

maFor us monitoring all the DNS servers log is not a option because we have so many DNS Servers spread over many locations.


O. Bor


L5 Sessionator
  • 1 replies
Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!

The LIVEcommunity thanks you for your participation!