Home ›

An Introduction to DNS and DNS Tools

Issue 85

From Issue #85
May 2001

May 01, 2001  By Neil Anuskiewicz
 in
The explosive growth of the Internet was made possible, in part, by DNS.
dig (domain information groper)

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.10
Wait 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.
nslookup

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.

Listing 2. Output with nslookup

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
Conclusion

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.

Neil Anuskiewicz lives and works in Portland, Oregon. When he is not sitting in front of a computer he likes to hike and climb. Write Neil an e-mail at neil@pacifier.com.

______________________

Comments

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

DNS server performance

Lukas's picture
Submitted by Lukas (not verified) on Sat, 05/14/2005 - 17:49.

For those of you, who don't just wanna make sure their dns system works properly but who are also interested in how fast their dns provider is, you can check your speed with this dns lookup tool.

White Paper
More Resources
Fabric-Based Computing Enables Optimized Hyperscale Data Centers

Today’s modular x86 servers are compute-centric, designed as a least common denominator to support a wide range of IT workloads. Those generic, virtualized IT workloads have much different resource optimization requirements than hyperscale and cloud applications. They have resulted in a “one size fits all” enterprise IT architecture that is not optimized for a specific set of IT workloads, and especially not emerging hyperscale workloads, such as web applications, big data, and object storage. In this report, you will learn how shifting the focus from traditional compute-centric IT architectures to an innovative disaggregated fabric-based architecture can optimize and scale your data center.

Learn More

Sponsored by AMD

White Paper
More Resources
Red Hat White Paper: Using an Open Source Framework to Catch the Bad Guy

Built-in forensics, incident response, and security with Red Hat Enterprise Linux 6

Every security policy provides guidance and requirements for ensuring adequate protection of information and data, as well as high-level technical and administrative security requirements for a system in a given environment. Traditionally, providing security for a system focuses on the confidentiality of the information on it. However, protecting the data integrity and system and data availability is just as important. For example, when processing United States intelligence information, there are three attributes that require protection: confidentiality, integrity, and availability.

Learn more about catching the bad guy in this free white paper.

Learn More

Sponsored by DLT Solutions