1Smokeping_probes_DNS(3)            SmokePing           Smokeping_probes_DNS(3)
2
3
4

NAME

6       Smokeping::probes::DNS - Name Service Probe for SmokePing
7

SYNOPSIS

9        *** Probes ***
10
11        +DNS
12
13        binary = /usr/bin/dig # mandatory
14        forks = 5
15        offset = 50%
16        step = 300
17        timeout = 15
18
19        # The following variables can be overridden in each target section
20        lookup = www.example.org
21        pings = 5
22        server = ns1.someisp.net
23
24        # [...]
25
26        *** Targets ***
27
28        probe = DNS # if this should be the default probe
29
30        # [...]
31
32        + mytarget
33        # probe = DNS # if the default probe is something else
34        host = my.host
35        lookup = www.example.org
36        pings = 5
37        server = ns1.someisp.net
38

DESCRIPTION

40       Integrates dig as a probe into smokeping. The variable binary must
41       point to your copy of the dig program. If it is not installed on your
42       system yet, you should install bind-utils >= 9.0.0.
43
44       The Probe asks the given host n-times for it's name. Where n is the
45       amount specified in the config File.
46

VARIABLES

48       Supported probe-specific variables:
49
50       binary
51           The location of your dig binary.
52
53           Example value: /usr/bin/dig
54
55           This setting is mandatory.
56
57       forks
58           Run this many concurrent processes at maximum
59
60           Example value: 5
61
62           Default value: 5
63
64       offset
65           If you run many probes concurrently you may want to prevent them
66           from hitting your network all at the same time. Using the probe-
67           specific offset parameter you can change the point in time when
68           each probe will be run. Offset is specified in % of total interval,
69           or alternatively as 'random', and the offset from the 'General'
70           section is used if nothing is specified here. Note that this does
71           NOT influence the rrds itself, it is just a matter of when data
72           acqusition is initiated.  (This variable is only applicable if the
73           variable 'concurrentprobes' is set in the 'General' section.)
74
75           Example value: 50%
76
77       step
78           Duration of the base interval that this probe should use, if
79           different from the one specified in the 'Database' section. Note
80           that the step in the RRD files is fixed when they are originally
81           generated, and if you change the step parameter afterwards, you'll
82           have to delete the old RRD files or somehow convert them. (This
83           variable is only applicable if the variable 'concurrentprobes' is
84           set in the 'General' section.)
85
86           Example value: 300
87
88       timeout
89           How long a single 'ping' takes at maximum
90
91           Example value: 15
92
93           Default value: 5
94
95       Supported target-specific variables:
96
97       lookup
98           Name of the host to look up in the dns.
99
100           Example value: www.example.org
101
102       pings
103           How many pings should be sent to each target, if different from the
104           global value specified in the Database section. Note that the
105           number of pings in the RRD files is fixed when they are originally
106           generated, and if you change this parameter afterwards, you'll have
107           to delete the old RRD files or somehow convert them.
108
109           Example value: 5
110
111       server
112           Name of the dns server to use.
113
114           Example value: ns1.someisp.net
115

AUTHORS

117        Igor Petrovski <pigor@myrealbox.com>,
118        Carl Elkins <carl@celkins.org.uk>,
119        Andre Stolze <stolze@uni-muenster.de>,
120        Niko Tyni <ntyni@iki.fi>,
121        Chris Poetzel<cpoetzel@anl.gov>
122
123
124
1252.7.2                             2019-02-02           Smokeping_probes_DNS(3)