01-29-2014
A recursive query (which by the way is the default setting in dig) has nothing to do with returning subdomains.
If a DNS server does not have the requested information when it receives a recursive query, it queries other DNS servers until it gets the information, or until the query fails.
9 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
if i wanted to ping all the machines in a given directory (/etc/hosts) and return a total count of responses how would i go about scripting that?
complete newbie...so be gentle
if ; then //$1 = /etc/hosts
cd "$1"
//this puts me into the directory i need...but how do i send ... (2 Replies)
Discussion started by: trostycp
2 Replies
2. Shell Programming and Scripting
I would have searched for this but I couldn't really think of what to use for the search text...
I've got a situation where I need to automate responses to an executable when running it from a script so that it can be made into a job the operators don't have to interact with. When I run it... (2 Replies)
Discussion started by: djp
2 Replies
3. Shell Programming and Scripting
Dear MoDs,
I have several doubts regarding query domain using DIG process..
below is my dig process:-
*********************************************
dns-dual# /usr/bin/dig @dns-dual.surfweb.net.my my soa
; <<>> DiG 9.3.0 <<>> @dns-dual.surfweb.net.my my soa
;; global options: ... (1 Reply)
Discussion started by: unknown2205
1 Replies
4. Linux
Unfortunately googling the word 'chat' gives you zebedee billion responses that relate to everything and few of them refer to the linux chat command. I've read the man page and found a couple of examples but can't see how to do this.
I want to query the modem for it's manufacturer, product id... (8 Replies)
Discussion started by: Bashingaway
8 Replies
5. Shell Programming and Scripting
Hello,
I am trying to count how many times a subject makes a correct switch or a correct stay response in a simple task. I have data on which condition they were in (here, labeled "IMAGINE" and "RECALL"), as well as whether they made a left or right button response, and whether the outcome was... (5 Replies)
Discussion started by: Jahn
5 Replies
6. What is on Your Mind?
Hi.
Having a bit of quick fun putting some networking tools online.
Here is a DNS Lookup tool.
It's basically the DIG command line tool wrapped in forum formatting.
If you want more features, please post here.
I'm doing to make a few more network tools like this and move on to other... (1 Reply)
Discussion started by: Neo
1 Replies
7. IP Networking
One of our email recipients has 17 mx records, and our emailing program postfix on linux does not retrieve these records. When using dig, the same thing happens.
This command returns no mx records
>dig mx fnb.co.za
But when using +trace, the records get returned
>dig mx fnb.co.za +trace
... (4 Replies)
Discussion started by: Joop Kaashoek
4 Replies
8. UNIX for Beginners Questions & Answers
In this script:
#!/bin/bash
# bird
read -p "Enter name of a bird "
REPLY=$REPLY
birdname="duck sparrow hawk"
for i in $birdname
do
if ]
then
echo "Yes, that is a bird."
else
echo "That is not a bird."
fi
done
I get... (9 Replies)
Discussion started by: Xubuntu56
9 Replies
9. Windows & DOS: Issues & Discussions
I have two DNS resolvers in /etc/resolv.conf file. The top one is Windows DNS server, and the bottom one is my wi-fi router. Please see below. nameserver 192.168.1.126 nameserver 192.168.1.1
In Windows DNS server, the sole "Forward Lookup Zone" is biman.net
When I query for host in the zone... (6 Replies)
Discussion started by: broy32000
6 Replies
LEARN ABOUT DEBIAN
smokeping_probes_dns
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)