An Introduction to DNS and DNS Tools
This powerful command gathers and returns DNS information in a format the name server can use directly. For this reason, dig is particularly useful in scripts. You will find it easy to query specific name servers with dig, making it a useful tool for narrowing down the source of DNS problems.
Suppose you have just transferred your domain name hosting from old-host.com to new-host.com. A customer sends you an e-mail saying he cannot reach your web site when he is logged into his ISP. You suspect the zone information simply has not had time to propagate. So, you find out what the NS records are for the ISP in question:
dig ns isp-in-question.com ;; ANSWER SECTION: isp-in-question.com. 10H IN NS ns1.hugeupstream.com. isp-in-question.com. 10H IN NS isp-in-question.com. isp-in-question.com. 10H IN NS ns.isp-in-question.com. isp-in-question.com. 10H IN NS ns.goodnameserver.com.
Then you check your company's web site against the ISP's name servers:
dig www.yourcompany.com @ns.isp-in-question.com ;; ANSWER SECTION: www.yourcompany.com. 59m53s IN A 192.168.5.10Wait a minute, that is your old IP address. It appears the DNS information has not fully propagated yet.
Next, you decide to see if old-host.com has removed the old zone information from their name servers. The “any” option will retrieve all the DNS information:
dig any www.yourcompany.com @ns.old-host.com ;; ANSWER SECTION: www.yourcompany.com. 1H IN A 192.168.200.250 ;; AUTHORITY SECTION: yourcompany.com. 1H IN NS webns.new-isp.com. yourcompany.com. 1H IN NS srvns.new-isp.com.
In this case the A record shows your new IP address for your web server, and it shows the new authoritative name servers for your domain name. This is the information you hoped to find.
These are the most useful dig query types: dig any (gathers all DNS information), dig ns (gathers name server information), dig mx (gathers mail exchanger information) and dig a (gathers network address information).
The dig command can also do reverse lookups with output formatted for the zone file:
dig -x 192.168.200.250 ;; ANSWER SECTION: 250.200.168.192.in-addr.arpa. 4h11s IN PTR www.yourcompany.com.
You can use this tool as a single line command, or you can use it interactively, which distinguishes it from the other DNS commands. Once you have started nslookup, type set all to list the default options. As with dig you can choose the server (name server) you want to query, and you can decide the type of DNS information on which to focus.
Just as you can issue commands to nslookup interactively, you can also change the initial defaults by starting a .nslookuprc file. The format of the .nslookup is one command per line:
set type=NS set domain=srvns.new-host.com set timeout=10
The ARPANET (the precursor to the Internet) had a few hundred hosts throughout the 1970s. A single flat file called HOSTS.TXT contained all of the information for every host. System administrators periodically downloaded the file and placed the information into their /etc/hosts file; take a look at your own /etc/hosts to see roughly what that file looked like. However, this system was not scalable. The advent of DNS made the exponential growth of the Internet possible.
- High-Availability Storage with HA-LVM
- Localhost DNS Cache
- DNSMasq, the Pint-Sized Super Dæmon!
- Real-Time Rogue Wireless Access Point Detection with the Raspberry Pi
- Days Between Dates: the Counting
- You're the Boss with UBOS
- The Usability of GNOME
- Linux for Astronomers
- Multitenant Sites
- PostgreSQL, the NoSQL Database