Sponsored Content
Full Discussion: I need help with...<various>
Top Forums Shell Programming and Scripting I need help with...<various> Post 302228207 by Habitual on Saturday 23rd of August 2008 12:50:40 PM
Old 08-23-2008
era:

coreutils-5.2.1-31.7 FWIW... Smilie

host -t ns example.com | while read dom ns server; do dig +short $dom; done
gives me:
208.77.188.166
208.77.188.166

and checking the data because we always do...

dig +short @b.iana-servers.net example.com
208.77.188.166
dig +short @a.iana-servers.net example.com
208.77.188.166

I still have work to do: "Dressing it up into the format you want is left as an exercise" Smilie

Thank you VERY much!
 
Smokeping_probes_DNS(3) 					     SmokePing						   Smokeping_probes_DNS(3)

NAME
Smokeping::probes::DNS - Name Service Probe for SmokePing SYNOPSIS
*** Probes *** +DNS binary = /usr/bin/dig # mandatory forks = 5 offset = 50% step = 300 timeout = 15 # The following variables can be overridden in each target section lookup = www.example.org pings = 5 server = ns1.someisp.net # [...] *** Targets *** probe = DNS # if this should be the default probe # [...] + mytarget # probe = DNS # if the default probe is something else host = my.host lookup = www.example.org pings = 5 server = ns1.someisp.net DESCRIPTION
Integrates dig as a probe into smokeping. The variable binary must point to your copy of the dig program. If it is not installed on your system yet, you should install bind-utils >= 9.0.0. The Probe asks the given host n-times for it's name. Where n is the amount specified in the config File. VARIABLES
Supported probe-specific variables: binary The location of your dig binary. Example value: /usr/bin/dig This setting is mandatory. forks Run this many concurrent processes at maximum Example value: 5 Default value: 5 offset If you run many probes concurrently you may want to prevent them from hitting your network all at the same time. Using the probe- specific offset parameter you can change the point in time when each probe will be run. Offset is specified in % of total interval, or alternatively as 'random', and the offset from the 'General' section is used if nothing is specified here. Note that this does NOT influence the rrds itself, it is just a matter of when data acqusition is initiated. (This variable is only applicable if the variable 'concurrentprobes' is set in the 'General' section.) Example value: 50% step Duration of the base interval that this probe should use, if different from the one specified in the 'Database' section. Note that the step in the RRD files is fixed when they are originally generated, and if you change the step parameter afterwards, you'll have to delete the old RRD files or somehow convert them. (This variable is only applicable if the variable 'concurrentprobes' is set in the 'General' section.) Example value: 300 timeout How long a single 'ping' takes at maximum Example value: 15 Default value: 5 Supported target-specific variables: lookup Name of the host to look up in the dns. Example value: www.example.org pings How many pings should be sent to each target, if different from the global value specified in the Database section. Note that the number of pings in the RRD files is fixed when they are originally generated, and if you change this parameter afterwards, you'll have to delete the old RRD files or somehow convert them. Example value: 5 server Name of the dns server to use. Example value: ns1.someisp.net AUTHORS
Igor Petrovski <pigor@myrealbox.com>, Carl Elkins <carl@celkins.org.uk>, Andre Stolze <stolze@uni-muenster.de>, Niko Tyni <ntyni@iki.fi>, Chris Poetzel<cpoetzel@anl.gov> 2.6.8 2013-03-17 Smokeping_probes_DNS(3)
All times are GMT -4. The time now is 10:23 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy