Sweet DNS

One can define the DNS in a single line; it is a distributed, hierarchical database where authority flows vertically downward from the top.

One can compare the structure of the DNS to an inverted tree. Every branch has one sector of authority; though, several branches of the tree can be confined to a particular zone.

The software which keeps the domain name information inside it is termed as a domain name server. The responsibility of command for several zones can be given to a single name server. Entire zones possess a primary master and a secondary master name server which delivers commanding rejoinder to their respective zones.

When a user is not getting a name server commanding for a particular zone, he/she can find that name server with the chances of timely information. This happens because of the reason that the zone information travels the entire net in frequent period of time, and name servers will grab that zone information also which is not in their commanding area.

DNS Commands

There are only three key commands and entire DNS information surrenders according to user’s requirements. One can try it by below mentioned ways:

Zone file database records splits DNS information into three chief categories i.e. NS (Name Server) records, MX (Mail Exchange) records, and A (Address) records. NS records designate the name servers. MX records designate the hosts that handle e-mail delivery; the priority (pri) number designates the sequence of utilization of mail servers, by way of lowest number being paid tot most concern. The A (Address) accounts map hostnames to IP addresses, the real names of machines.

Host

One which is straightforward in comparison to all DNS commands. Shortest way to resolve the IP address of a hostname:

: host www.my-domain-name.com

The -a option, transforms entire DNS information into verbose format.

: Host -a www.my-domain-name.com

As, user recognize the IP address for www.my-domain-name.com, take a reverse gear.

: host IP-ADDRESS

Dig i.e. domain information groper

The function of this command is to collect and return back all the DNS information in a format where straightforward application of it is possible by the name server. One can easily enquire about specific name servers in the company dig.

One can rapidly verify the Name servers of his/her host or any unfamiliar host:

: dig ns my-host.com

After that on should verify his/her or other’s website beside the host’s name servers:

: dig www.my-domain-name.com @ns.my-host.com

Dig also has the potential can provide yield in the same set-up as in zone file. Here is the way:

: dig any my-domain-name.com

Most applicable dig query types are the next: dig any (collects entire DNS information), dig ns (collects name server information), dig mx (collects mail exchanger information) and dig a (collects network address information).

The dig command can also do reverse lookups with output formatted for the zone file:

: dig -x IP-Address

Nslookup

One can apply this weapon as a single line command, or apply it for an interaction purpose, which keep it as outstanding from additional DNS commands. Once the user began nslookup, he/she should type set all to list the default options. With dig one can choose desired server he/she wants to query, and one can also decide the selection of any DNS information as desired.

Just as user issues commands to nslookup interactively, he/she 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.my-host.com

set timeout=10

Conclusion

When the user applies the three above mentioned commands he/she can get all necessary information about his/her domain names. These are dominant weapons, and through the means of this article one can enhance so much information to get geared up and lead.