1Smokeping_probes_AnotherDNS(3)     SmokePing    Smokeping_probes_AnotherDNS(3)
2
3
4

NAME

6       Smokeping::probes::AnotherDNS - Alternate DNS Probe
7

SYNOPSIS

9        *** Probes ***
10
11        +AnotherDNS
12
13        forks = 5
14        offset = 50%
15        step = 300
16
17        # The following variables can be overridden in each target section
18        authoritative = 0
19        ipversion = 4
20        lookup = www.example.org
21        mininterval = 0.5
22        pings = 5
23        port = 53
24        protocol = udp
25        recordtype = A
26        require_answers = 0
27        require_noerror = 0
28        timeout = 5
29
30        # [...]
31
32        *** Targets ***
33
34        probe = AnotherDNS # if this should be the default probe
35
36        # [...]
37
38        + mytarget
39        # probe = AnotherDNS # if the default probe is something else
40        host = my.host
41        authoritative = 0
42        ipversion = 4
43        lookup = www.example.org
44        mininterval = 0.5
45        pings = 5
46        port = 53
47        protocol = udp
48        recordtype = A
49        require_answers = 0
50        require_noerror = 0
51        timeout = 5
52

DESCRIPTION

54       Like DNS, but uses Net::DNS and Time::HiRes instead of dig. This probe
55       does *not* retry the request three times before it is considerd "lost",
56       like dig and other resolver do by default. If operating as caching
57       Nameserver, BIND (and maybe others) expect clients to retry the request
58       if the answer is not in the cache. So, ask the nameserver for something
59       that he is authoritative for if you want measure the network packet
60       loss correctly.
61
62       If you have a really fast network and nameserver, you will notice that
63       this probe reports the query time in microsecond resolution. :-)
64

VARIABLES

66       Supported probe-specific variables:
67
68       forks
69           Run this many concurrent processes at maximum
70
71           Example value: 5
72
73           Default value: 5
74
75       offset
76           If you run many probes concurrently you may want to prevent them
77           from hitting your network all at the same time. Using the probe-
78           specific offset parameter you can change the point in time when
79           each probe will be run. Offset is specified in % of total interval,
80           or alternatively as 'random', and the offset from the 'General'
81           section is used if nothing is specified here. Note that this does
82           NOT influence the rrds itself, it is just a matter of when data
83           acqusition is initiated.  (This variable is only applicable if the
84           variable 'concurrentprobes' is set in the 'General' section.)
85
86           Example value: 50%
87
88       step
89           Duration of the base interval that this probe should use, if
90           different from the one specified in the 'Database' section. Note
91           that the step in the RRD files is fixed when they are originally
92           generated, and if you change the step parameter afterwards, you'll
93           have to delete the old RRD files or somehow convert them. (This
94           variable is only applicable if the variable 'concurrentprobes' is
95           set in the 'General' section.)
96
97           Example value: 300
98
99       Supported target-specific variables:
100
101       authoritative
102           Send non-recursive queries and require authoritative answers.
103
104           Default value: 0
105
106       ipversion
107           The IP protocol used. Possible values are "4" and "6".  Passed to
108           echoping(1) as the "-4" or "-6" options.
109
110           Example value: 4
111
112           Default value: 4
113
114       lookup
115           Name of the host to look up in the dns.
116
117           Example value: www.example.org
118
119       mininterval
120           Minimum time between sending two lookup queries in (possibly
121           fractional) seconds.
122
123           Default value: 0.5
124
125       pings
126           How many pings should be sent to each target, if different from the
127           global value specified in the Database section. Note that the
128           number of pings in the RRD files is fixed when they are originally
129           generated, and if you change this parameter afterwards, you'll have
130           to delete the old RRD files or somehow convert them.
131
132           Example value: 5
133
134       port
135           The UDP Port to use.
136
137           Default value: 53
138
139       protocol
140           The Network Protocol to use.
141
142           Default value: udp
143
144       recordtype
145           Record type to look up.
146
147           Default value: A
148
149       require_answers
150           Only Count Answers with answer count >= this value.
151
152           Default value: 0
153
154       require_noerror
155           Only Count Answers with Response Status NOERROR.
156
157           Default value: 0
158
159       timeout
160           Timeout for a single request in seconds.
161
162           Default value: 5
163

AUTHORS

165       Christoph Heine <Christoph.Heine@HaDiKo.DE>
166
167
168
1692.7.2                             2019-02-02    Smokeping_probes_AnotherDNS(3)
Impressum