3.BIND configuration from server and cache server

I. Domain slave server

A domain's slave server (slave) is typically used for backup and load balancing, and all information for this domain is controlled by the domain's primary server, and when the domain slave server starts, it fetches the zone profile of the specified domain from the domain's primary server (master), and the domain slave server is configured as follows:

1. Add the definition of the domain in the main configuration file of bind

2. Start the BIND service or enable bind refresh configuration

3. See if the zone file of the domain is properly crawled into the/var/named/slaves directory

4. Use the host or dig command to detect if domain information is normal

two. Domain Slave server

Linuxcast.net.zone

Slave--------------------> Master

192.168.1.11 192.168.1.10

Three. Configure the domain from the server

1. Add the configuration information from the domain Linuxcast.net in the main configuration file of bind:

1. configuration file Location:

/var/named/chroot/etc/named.conf

2. Add a zone definition for a row of fields in the master configuration file:

1 " linuxcast.net " {2        type slave; 3         masters{10.10.  10.10;}; 4         file " Slaves/linuxcast.net.zone " ; 5     };

2. Restart the BIND service or refresh the configuration:

Service named start

Service named Reload

3. Check to see if the zone file is properly crawled:

/var/named/chroot/var/named/slaves/linuxcast.net.zone

4. Point the DNS configuration of this computer to this machine:

/etc/resolv.conf; NameServer 127.0.0.1

5. Use the command host or dig to verify the DNS configuration:

Host Www.linuxcast.net

Dig www.linuxcast.net

Four. Configure the cache server

A DNS server can be neither a master server for a domain nor a slave server for a domain, a server can have no configuration information for any domain, it will recursively parse all the DNS queries it receives, return the results to the query client, and cache the query results. Such a DNS server is called caching name server.

1. Cache servers are typically configured in a local area network to speed up access to networks

2. You can also configure an upstream DNS server address for the cache server, which can provide the client with an upstream DNS server address, which we can do through the following settings:

forwarders{218.30.19.40;};

You can also use the following options to have the server forward all DNS queries to the forwarders server;

Forward only;

Note:

1. Configuration from the server must be the/var/named/chroot/var/named/slaves directory permissions to change to named:named and readable writable, otherwise unable to sync

2. You must set the permissions in the pseudo-root directory to be readable, otherwise it will not resolve correctly

3. Turn off the firewall and SELinux

4. The master server's/var/named/chroot/etc/named.conf configuration file must be changed to listen on all ports, that is, 127.0.0.1 comments, otherwise it cannot be accessed from the server.

3.BIND configuration from server and cache server