net.tcp.dns always returns 1

[zeki893]

i setup net.tcp.dns[<ip of my dns server>,krypt.com] and it only returns 1. I turned off named service and it still returns 1. Is it possible it is using the dns server on the localhost?

[makini]

Nop...

We tested and use this specific item to monitor a local caching daemon, (e.g. net.tcp.dns[127.0.0.1,some.domain.com]) and it seems to work fine - when daemon is down it does return 0.

Server is v1.6.1 & agent is 1.1.1

[zeki893]

i'm using 1.6.2 server and 1.6.2 agent

[makini]

Now I have a question related to this...

In the recent doc file (1.6 rev 17),
in Agent supported parameters table, there's a comment for net.tcp.dns[ip, zone] - the "IP address of DNS server" has "(ignored)" added in the end. Does this mean the Agent is ignoring the DNS server address you specify as the parameter and tests resolving with local machine's configured DNS servers? If not, what does it mean?

[vinny]

Hi all,
I have also some issue using this function.

On the paper, that looks quite interesting but could someone explain the internal functionment of net.tcp.dns ?

vinny