Probe DNS

Unanswered Question
Feb 12th, 2009

Dear

I have a probe DNS , but by someone reason, in spite that the service DNS is up, the probe show that down. I tried putting domain and expect, but the results are the same. The process is the next:

a) First time detect service up.

b) Service is down, the probe detect the fail.Rserver is down.

c) The service is put up. But the probe never detect the service up.

See the next picture:

ACE4710-1/IIS# show probe DNS detail

probe : DNS

type : DNS

state : ACTIVE

description : "test de DNS"

----------------------------------------------

port : 53 address : 0.0.0.0 addr type : -

interval : 30 pass intvl : 300 pass count : 3

fail count: 3 recv timeout: 10

dns domain : www.cisco.com

--------------------- probe results --------------------

probe association probed-address probes failed passed health

------------------- ---------------+----------+----------+----------+-------

rserver : DNS1-G

10.1.5.20 17 5 12 FAILED

Socket state : CLOSED

No. Passed states : 1 No. Failed states : 1

No. Probes skipped : 0 Last status code : 0

No. Out of Sockets : 0 No. Internal error: 0

Last disconnect err : Connection refused by server

Last probe time : Wed Feb 11 20:17:12 2009

Last fail time : Wed Feb 11 20:16:42 2009

Last active time : Wed Feb 11 19:57:12 2009

rserver : DNS1-N

10.1.5.12 29 5 24 FAILED

Socket state : CLOSED

No. Passed states : 0 No. Failed states : 1

No. Probes skipped : 0 Last status code : 0

No. Out of Sockets : 0 No. Internal error: 0

Last disconnect err : Connection refused by server

Last probe time : Wed Feb 11 20:21:17 2009

Last fail time : Wed Feb 11 20:20:47 2009

Last active time : Tue Feb 10 22:03:17 2009

admin dns DNS

DOMAIN WWW.CISCO.COM

expect 198.133.219.25

Best Regards

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
Gilles Dufour Fri, 02/13/2009 - 03:13

Your server does not respond

"Connection refused by server "

Get a sniffer trace to confirm if you want.

Gilles.

rodrigo.hernandez Fri, 02/13/2009 - 05:07

Thaks mister

But the problem is a little more complex. I do a telnet at the port 53 and the server respond. In the same way, I do a nslookup to the server, and the server respond all query ....

Best Regards

Gilles Dufour Fri, 02/13/2009 - 08:36

It does response to your pc, but not to ACE.

Or the response never makes it to ACE.

Either because of routing issue.

Or because it is dropped by an ACL.

Could even be an ACL on ACE itself.

Again, a sniffer trace to confirm that the response makes it to ACE.

G.

Actions

This Discussion