January 13, 2008 · General ·

Sponsored Link
If you manage Domain Name System (DNS) records, you probably already know how seemingly minor errors can cause big problems. Leaving a semicolon off the end of a statement, forgetting the trailing period, or failing to add that right bracket can cause a DNS server to fail to load or to respond incorrectly to requests. Dlint is a utility that will check your domains for common errors, allowing you to fix them before a problem gets out of hand. Dlint uses Domain Information Groper (DiG) and a combination shell/Perl script to gather and parse DNS information. This script can help verify your configuration and save you some troubleshooting time in the future.

Install dlint in ubuntu

sudo aptitude install dlint

This will comple the installation

Using Dlint

You can run Dlint against any domain on the Internet, not just ones you administer. Since it uses DiG to gather DNS information, it can work with information gathered from any DNS server.

Dlint Examples

1) dlint nau.edu.

The above command recursively scans the DNS records in zone nau.edu for problems.

2) dlint 64.114.134.in-addr.arpa.

The above command recursively scans the DNS records associated with IP subnet 134.114.64.0 for problems. You had to already know that 134.114.0.0 was subnetted.

3)You can also specify a nonrecursive check with the –n command-line option. Dlint will automatically find the primary and secondary name servers for the supplied domain and attempt to do a zone transfer (AXFR).

example

dlint -n google.com

output looks similar to the following screen

Administration of DNS, especially in a large-scale environment, can be difficult to keep up with. Constant changes can leave holes or misconfigurations on your DNS server. Dlint will check DNS records for a domain and attempt to find possible errors, offering a quick-and-easy way to keep your DNS database viable and up to date.

Sponsored Link

Leave a Reply

  • Recent comments