Subdomain Authorization and view

Subdomain authorization

Subdomain authorization to partition a small area on the original domain and specify a new DNS server. In this small area, if there is a client request resolution, just look for a new child DNS server. The benefits of doing so can relieve the stress of the primary DNS and also facilitate management. This time, only the subdomain of the positive zone is authorized.

The name server of each domain is authorized by its parent name server in the parsing library;

Similar to the root domain authorized TLD:

. com.in NS ns1.com.

. com. In NS ns2.com.

ns1.com. in A 2.2.2.1

ns2.com. in A 2.2.2.2

Magedu.com. On the. COM name server, add a resource record to the resolution library:

magedu.com. in NS ns1.magedu.com.

magedu.com. in NS ns2.magedu.com.

magedu.com. in NS ns3.magedu.com.

ns1.magedu.com. in A 3.3.3.1

ns2.magedu.com. in A 3.3.3.2

ns3.magedu.com. in A 3.3.3.3

Glue Record: Adhesive records

View

View is a zone of a collection, easy to manage zone, if you do not have a view, then they belong to a view, the basic can be understood. He can split the DNS, it is this feature to allow us to facilitate the implementation of different inbound and outbound management.

Implementation of the function: The machine is located in all the machines issued by the request to resolve, in addition, the host of the machine can be reverse-resolved.

View:

A BIND server can define multiple view, one or more zones can be defined in each view;

Each view matches a set of clients;

Multiple view may need to parse the same area, but use different zones to parse the library file;

View View_name {

match-clients {};

}

Attention:

(1) Once the view is enabled, all zones can only be defined in the view;

(2) It is only necessary to define the root area in the view that matches the client that allows the recursive request;

(3) When a client request arrives, the list of clients serviced by each view is checked from top to bottom

Subdomain Authorization and view