I am trying to add a DNS sensor to one of my DNS servers but keep getting a No Response PE002 error code. I have verified that the DNS service is running and it is serving dns requests correctly. My ping sensor is working fine. I am able to telnet to the server on port 53.
I have a total of three DNS servers. Two in my local office and a third (the one in question) is in a remote office connect via vpn. The dns sensors on the two in my local office are working fine, it's just the remote one throwing this error. Hoping someone can point me in the right direction to get this resolved.
Article Comments
Yes, a port sensor works correctly. I also did an nmap scan of the target and port 53 shows open.
Aug, 2017 - Permalink
Instead of trying to check these devices over a vpn, I installed a remote probe at that location and it is able to check DNS fine so I will leave it like that. Didn't know about the remote probe at first or I would have just gone that route.
Aug, 2017 - Permalink
Yep, that works as well :) Somehow my answer wasn't posted, stating that you should tap the connection with WireShark to see if the correct DNS gets queried by the probe.
But since it's working now, I'd leave it like that :)
Kind regards,
Stephan Linke, Tech Support Team
Aug, 2017 - Permalink
Hi Arstacey,
When you create a port sensor for port 53 on the device, does that one work properly?
Kind regards,
Stephan Linke, Tech Support Team
Aug, 2017 - Permalink