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        /^influx_.+/ = influx_location = In the basement
19        authoritative = 0
20        expect_text = 192.168.50.60
21        ipversion = 4
22        lookup = www.example.org
23        mininterval = 0.5
24        pings = 5
25        port = 53
26        protocol = udp
27        recordtype = A
28        require_answers = 0
29        require_noerror = 0
30        require_nxdomain = 0
31        timeout = 5
32
33        # [...]
34
35        *** Targets ***
36
37        probe = AnotherDNS # if this should be the default probe
38
39        # [...]
40
41        + mytarget
42        # probe = AnotherDNS # if the default probe is something else
43        host = my.host
44        /^influx_.+/ = influx_location = In the basement
45        authoritative = 0
46        expect_text = 192.168.50.60
47        ipversion = 4
48        lookup = www.example.org
49        mininterval = 0.5
50        pings = 5
51        port = 53
52        protocol = udp
53        recordtype = A
54        require_answers = 0
55        require_noerror = 0
56        require_nxdomain = 0
57        timeout = 5
58

DESCRIPTION

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

VARIABLES

72       Supported probe-specific variables:
73
74       forks
75           Run this many concurrent processes at maximum
76
77           Example value: 5
78
79           Default value: 5
80
81       offset
82           If you run many probes concurrently you may want to prevent them
83           from hitting your network all at the same time. Using the probe-
84           specific offset parameter you can change the point in time when
85           each probe will be run. Offset is specified in % of total interval,
86           or alternatively as 'random', and the offset from the 'General'
87           section is used if nothing is specified here. Note that this does
88           NOT influence the rrds itself, it is just a matter of when data
89           acquisition is initiated.  (This variable is only applicable if the
90           variable 'concurrentprobes' is set in the 'General' section.)
91
92           Example value: 50%
93
94       step
95           Duration of the base interval that this probe should use, if
96           different from the one specified in the 'Database' section. Note
97           that the step in the RRD files is fixed when they are originally
98           generated, and if you change the step parameter afterwards, you'll
99           have to delete the old RRD files or somehow convert them. (This
100           variable is only applicable if the variable 'concurrentprobes' is
101           set in the 'General' section.)
102
103           Example value: 300
104
105       Supported target-specific variables:
106
107       /^influx_.+/
108           This is a tag that will be sent to influxdb and has no impact on
109           the probe measurement. The tag name will be sent without the
110           "influx_" prefix, which will be replaced with "tag_" instead. Tags
111           can be used for filtering.
112
113           Example value: influx_location = In the basement
114
115       authoritative
116           Send non-recursive queries and require authoritative answers.
117
118           Default value: 0
119
120       expect_text
121           A string that should be present in the DNS answer. This can be used
122           to verify that an A record contains the expected IP address, a PTR
123           record reflects the expected hostname, etc. If the query returns
124           multiple records, any single match will pass the test.
125
126           Example value: 192.168.50.60
127
128       ipversion
129           The IP protocol used. Possible values are "4" and "6".  Passed to
130           echoping(1) as the "-4" or "-6" options.
131
132           Example value: 4
133
134           Default value: 4
135
136       lookup
137           Name of the host to look up in the dns.
138
139           Example value: www.example.org
140
141       mininterval
142           Minimum time between sending two lookup queries in (possibly
143           fractional) seconds.
144
145           Default value: 0.5
146
147       pings
148           How many pings should be sent to each target, if different from the
149           global value specified in the Database section. Note that the
150           number of pings in the RRD files is fixed when they are originally
151           generated, and if you change this parameter afterwards, you'll have
152           to delete the old RRD files or somehow convert them.
153
154           Example value: 5
155
156       port
157           The UDP Port to use.
158
159           Default value: 53
160
161       protocol
162           The Network Protocol to use.
163
164           Default value: udp
165
166       recordtype
167           Record type to look up.
168
169           Default value: A
170
171       require_answers
172           Only Count Answers with answer count >= this value.
173
174           Default value: 0
175
176       require_noerror
177           Only Count Answers with Response Status NOERROR.
178
179           Default value: 0
180
181       require_nxdomain
182           Set to 1 if NXDOMAIN should be interpreted as success instead of
183           failure. This reverses the normal behavior of the probe. Example
184           uses include testing a DNS firewall, verifying that a mail server
185           IP is not listed on a DNSBL, or other scenarios where NXDOMAIN is
186           desired.
187
188           Example value: 0
189
190           Default value: 0
191
192       timeout
193           Timeout for a single request in seconds.
194
195           Default value: 5
196

AUTHORS

198       Christoph Heine <Christoph.Heine@HaDiKo.DE>
199
200
201
2022.8.2                             2023-01-21    Smokeping_probes_AnotherDNS(3)
Impressum