DNS chapter II (BIND usage)

Source: Internet
Author: User
Tags dnssec

Internet Domain Name space
Internet domain name structure is an inverted tree, and hierarchical division.

The tree roots to the branches, that is, from the DNS root to the following nodes, according to different levels, the unified naming.

At the top level of the domain name space, the DNS root is called the root domain (root).

The next level of the root domain is the top-level domain, also known as a first-level domain.

The lower layer is a two-level domain, and then the sub-domain of the two-level domains, as required to plan, can be multilevel.

Therefore, the domain name space as a whole, from the topmost to the lower level, can be divided into: root domain, top-level domain (first-level domain)

A secondary domain, a subdomain, in which a domain can contain hosts and subdomains.


Zone domains: domain, logical concept
Zone: Zone, physical concept

Zone is a contiguous part of the DNS namespace that contains a set of stored in DNS
resource records on the server. Each zone is located in a special domain node, but the zone is not a domain.
A DNS domain is a branch of a namespace, and a zone is typically stored in a
A part of a DNS namespace in a piece of a component that can include multiple domains. A domain can
To split into parts, each section or area can be controlled by a DNS server.
Using the concept of zones, the DNS server answers queries about the hosts in its own area, which is the authoritative server for the zone.


Forward parsing and reverse parsing
The forward and backward parsing techniques are different and therefore should not be stored in the same database file

1) Forward parsing
Forward parsing refers to the process of resolving a domain name to an IP address.

2) Reverse parsing
Reverse parsing is the process of parsing from an IP address to a domain name. The role of reverse parsing is the authentication of the server.


A basic overview of bind:

Master profile: Define zone/etc/named.conf

1 options {       listen-on port 53 {  172.16.249.24; };       listen-on-v6 port 53 { ::1 ; };       directory        "/var/ Named ";       dump-file       "/var/ Named/data/cache_dump.db ";       statistics-file "/var/named/data/ Named_stats.txt ";       memstatistics-file "/var/named/data/named_mem_ Stats.txt ";        allow-query     { localhost ; };       recursion yes;                dnssec-enable yes;        dnssec-validation yes;       dnssec-lookaside auto;         /* Path to ISC DLV key */         bindkeys-file  "/etc/named.iscdlv.key";         managed-keys-directory  "/var/named/dynamic";}; 2 logging {        channel default_debug {                 file  "data/ Named.run ";                 severity dynamic;        };  3  zone  "."  IN {        type hint;         file  "named.ca";};

Forward parsing

Define the configuration file field as "Wowowo.com"

Options {directory "/var/named";}; Zone "."        in {type hint; File "named.ca";}; Zone "localhost."        in {type Master; File "Named.localhost";};        Zone "1.0.0.127.in-addr.arpa" in {type Master; File "Named.loopback";}; Zone "wowowo.com."        in {type Master; File "Wowowo.com.zone";};

The file name in the resource record must match the name defined in the configuration file
Configure resource records

$TTL  600@       IN      SOA      dns.wowowo.com. admin.wowowo.com.  (                          2015020001                         2H                         10M                          7D                         1D)         in       ns      dns.wowowo.com.        IN       MX 10   maildns     IN       a       192.168.1.110mail    in       A       192.168.1.111www      IN      A        192.168.1.110ftp     in      cname   www

Direction resolution

Zone "1.168.192.in-addr.arpa."        in {type Master; File "192.168.1.zone";}; Syntax format

Format of resource records

$TTL  600@       IN      SOA      dns.wowowo.com. admin.wowowo.com.  (                          2015020002                         2H                         10M                          7D                         1D)         in       ns      dns.wowowo.com.110     IN       PTR     dns.wowowo.com.110     IN       ptr     www.wowowo.com.111     in       ptr     mail.wowowo.com.


Master-Slave: (BIND version can be lower than the slave)

To add a critical two-step from the server to the zone
Authorized in the Superior
Add an NS record and a corresponding A or PTR record in the zone data file for the slave server

The format is forward (reverse) synchronization of the zone "wowowo.com" in {type slave; masters {192.168.1.110;}; Aves/wowowo.com.zone "; 46}; "1.168.192.in-addr.arpa" in {type slave; masters {192.168.1.110;}; Slaves/192.168.1.zone "; 52};

Resource record configuration (on the primary server to add a pair of NS records from the server, otherwise the update from the server will not be notified)

Primary server/var/named/forward configuration format $ttl 600  @       in       SOA     dns.wowowo.com. admin.wowowo.com.  (                          2015020005                         3M                         6m                          9M                         1D)          IN      NS      dns.wowowo.com.         IN      NS       dns1.wowowo.com.        in      mx  10   maildns     in      a        192.168.1.110mail    in      a        192.168.1.111dns1    IN       A       192.168.1.108www     IN       A       192.168.1.110ftp      IN      CNAME   wwwimg      in       a       192.168.1.112 
Reverse Configuration Format $ttl 600@       in      soa      dns.wowowo.com. admin.wowowo.com.  (                          2015020004                         2H                         10M                          7D                         1D)         in      &nBsp ns      dns.wowowo.com.        in       NS      dns1.wowowo.com.110      IN      PTR     dns.wowowo.com.110      IN      PTR      www.wowowo.com.111     in      ptr      mail.wowowo.com.108     IN      PTR      dns1.wowowo.com.112     IN       ptr     img.wowowo.com.




DNS chapter II (BIND usage)

Contact Us

The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion; products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the content of the page makes you feel confusing, please write us an email, we will handle the problem within 5 days after receiving your email.

If you find any instances of plagiarism from the community, please send an email to: info-contact@alibabacloud.com and provide relevant evidence. A staff member will contact you within 5 working days.

A Free Trial That Lets You Build Big!

Start building with 50+ products and up to 12 months usage for Elastic Compute Service

  • Sales Support

    1 on 1 presale consultation

  • After-Sales Support

    24/7 Technical Support 6 Free Tickets per Quarter Faster Response

  • Alibaba Cloud offers highly flexible support services tailored to meet your exact needs.