07-06-2001
Yes, just another DNS tool like nslookup. You do a man on dig and read the man page, or look at the command line switches.
You use it when you are querying DNS servers for information and/or troubleshooting DNS configurations (just like nslookup).
BTW: Many people really dig dig. I still dig nslookup, dig?
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi all, I'm running BIND 9.1.3 and the accompanying `dig and nslookup' on a vanilla Redhat 7.2 Linux box.
I've produced all of my Zone data and config files (I used h2n with some manual tweaks to do this, as some >= v8.2 BIND features aren't properly supported as far as I can see).
Im my... (6 Replies)
Discussion started by: sam_pointer
6 Replies
2. Shell Programming and Scripting
First I would like to thank you for your time in running a great Forum!
Background - Windows/ASP/VB COM/SQL Server programmer/Webmaster.
Desire - To build similar skillset on UNIX. I am looking at learning Perl or Python (maybe Jython due to connection to Java). I have a brief background... (3 Replies)
Discussion started by: nimrod
3 Replies
3. UNIX for Dummies Questions & Answers
When I use the linux dig command such as #dig yahoo.com it resolves
but when I use the same command as root it gives me error "Segmentation Fault"
Please advise I am completly baffled. (1 Reply)
Discussion started by: Tirmazi
1 Replies
4. UNIX for Dummies Questions & Answers
all,
i am newbie to dns bind . Any help is very appreciated.
I am using dig command to view the records in the config. I am expecting the following comamnds to display all the A (Address records) in the zone data file.
my zone data file looks like this
-------------------
$ORIGIN .
$TTL... (2 Replies)
Discussion started by: sujathab
2 Replies
5. UNIX for Dummies Questions & Answers
Hi Guys,
I just need a confirmation if what think i know is right .
dig yahoo.com
; <<>> DiG 9.7.0-P1 <<>> yahoo.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 27410
;; flags: qr rd ra; QUERY: 1, ANSWER: 5, AUTHORITY: 0, ADDITIONAL: 0
... (1 Reply)
Discussion started by: mtomar
1 Replies
6. IP Networking
Can I use two different DNS servers in the one command in the form of primary and secondary.
Take this for example:
dig @<primaryAddress> @<secondaryAddress> MX domain.tld
So if primary address is down, it will use the secondary address as a backup. It seems to work when testing, but thought... (1 Reply)
Discussion started by: neil_is_ere
1 Replies
7. UNIX for Advanced & Expert Users
Hi,
I have these entries in the /etc/esolv.conf:
------------
domain xxxxxx
search yyyyyy
nameserver 127.0.0.1
nameserver aaaaaaaaaaaaaaaa
nameserver bbbbbbbbbbbbbbbb
-------------
When I use 'dig' or 'nslookup' command, like 'dig yahoo.com' it uses the localhost as the server.
I... (2 Replies)
Discussion started by: chaandana
2 Replies
8. 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
9. Shell Programming and Scripting
Hi,
I am testing some code to match a grep to see if one of the dns server exists but it does not seem to match:
ERROR:
=======
CRITICAL: google.com DNS : ns3.google.com NOT found
CODE:
=====
if ; then
echo "OK: google.com DNS : ns3.google.com exists"
else
echo... (5 Replies)
Discussion started by: dmccabe
5 Replies
10. Shell Programming and Scripting
Experts - I was hoping someone could help me out with the logic on this perl script.
I'm trying to run some dig commands and parse in such a way as to group them together.
Here's what I have so far.
#!/usr/bin/perl
system(clear);
my @host = qw/yahoo.com
google.com
/;
foreach... (2 Replies)
Discussion started by: timj123
2 Replies
LEARN ABOUT SUNOS
nisd_resolv
rpc.nisd_resolv(1M) System Administration Commands rpc.nisd_resolv(1M)
NAME
rpc.nisd_resolv, nisd_resolv - NIS+ service daemon
SYNOPSIS
rpc.nisd_resolv [-v | -V] [ -F [-C fd]] [-t xx] [-p yy]
DESCRIPTION
rpc.nisd_resolv is an auxiliary process which provides DNS forwarding service for NIS hosts requests to both ypserv and rpc.nisd that are
running in the NIS compatibility mode. It is generally started by invoking rpc.nisd(1M) with the -B option or ypserv(1M) with the -d
option. Although it is not recommended, rpc.nisd_resolv can also be started independently with the following options.
This command requires that the /etc/resolv.conf file be setup for communication with a DNS nameserver. The nslookup utility can be used to
verify communication with a DNS nameserver. See resolv.conf(4) and nslookup(1M).
OPTIONS
-F Run in foreground.
-C fd Use fd for service xprt (from nisd).
-v Verbose. Send output to the syslog daemon.
-V Verbose. Send output to stdout.
-t xx Use transport xx.
-p yy Use transient program# yy.
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWnisu |
+-----------------------------+-----------------------------+
SEE ALSO
nslookup(1M), rpc.nisd(1M), resolv.conf(4), attributes(5)
NOTES
NIS+ might not be supported in future releases of the SolarisTM Operating Environment. Tools to aid the migration from NIS+ to LDAP are
available in the Solaris 9 operating environment. For more information, visit http://www.sun.com/directory/nisplus/transition.html.
SunOS 5.10 12 Dec 2001 rpc.nisd_resolv(1M)