// // See /usr/share/doc/bind*/sample/ for example named configuration files.// options ; logging ; zone "." IN ; include "/etc/named.rfc1912.zones"; include "/etc/key"; ### ELinux Book Internal Zones ### ### Forward Zone ### zone "elinuxbook.com" IN ; ### Reverse Zone ### zone "1.168.192.in-addr.arpa" IN ; The syntax of zone data files lends itself to making mistakes.It doesn't help that the address and pointer records are in different files, which must agree with each other.
But with this polling scheme, it can take up to the refresh interval before a slave detects and transfers new zone data from its master name server.( Main Configuration File ), for ( Forward Zone ), rev ( Reverse Zone ) to allow the Query and Zone record transfer to Slave Server.Let’s go ahead and configure the /etc/in Master Server. // // // // Provided by Red Hat bind package to configure the ISC BIND named(8) DNS // server as a caching only nameserver (as a localhost DNS resolver only). Ideally, DNS server consist of 2 machines that work together simultaneously, one act as master and the other one act as slave.If your domain registrar doesn’t provide you a free DNS server, or if you want to create a custom DNS record, then you might need to host your own DNS server.