Configurations on Master server are now complete, we will now configure our slave server to receive zone transfers from Master DNS. Firstly, we will install BIND on slave. Open named. Then we will add our network, to allow clients from our network to make query to DNS. So add the following line.
Every time we make an update to the master, the master will notify the slave which in turn will fetch the update, thus keeping both master-slaves in sync.
If you think we have helped you or just want to support us, please consider these Connect to us: Facebook Twitter. To make things simple, we are going to show you the original file copied from the Master DNS and the modified version which now sits on the Slave DNS server. The Master named. To help you identify the changes, we have marked them in red:.
As you can see, most of the slave's named. The type value is now slave , and that's pretty logical since it tells the dns server if it's a master or slave. The file " bak. We tend to follow the bak. It is not imperative to use this name scheme, you can change it to whatever you wish.
The first of these is the more likely explanation. The log should contain enough information to identify the cause. You can check whether an initial zone transfer has occurred by looking for the zone file. This is the argument to the file statement in the zone declaration:.
The file should have been created by named , and have content equivalent to but probably not identical to the master zone file on ns0. You can check the first four points by viewing DNS traffic to and from ns1 using tcpdump :. If ns0 refused to transfer the zone then this should be recorded in the log on ns0 , for example:.
If the transfer occurred but the file could not be written then this should be recorded in the log on ns1 , for example:.
You can check whether ns0 is notifying ns1 by using tcpdump to view the traffic:. If notifications are not being sent or logged then you should check that they are enabled for the zone in question, and that ns1 is either:.
Subsequent zone transfers can be viewed in the same way as the initial transfer, but may be considerably smaller if you have enabled the use of incremental transfers.
The most likely reason for the slave not requesting a transfer when it has received a notification is if it already has a copy of the zone with the same or a more recent serial number. In that case you should advance the serial number of the master zone file until it is greater than that of the slave zone file. You should look for a relevant allow-transfer statement in the configuration of ns0 and add ns1 to the list. You should not attempt to fix this by granting write access to that directory: there are good security reasons why named should only have read access to its configuration.
Instead you should write the zone file to some other location. For example:. Doing this reduces the risk of specifying the wrong IP address, and simplifies the task of changing the address should this ever be necessary. Danger, Will Robinson: this website uses cookies. The script initiates the rndc command for each connected slave server. Slave servers synchronize domain zones with the ones on the Plesk server.
Is this page helpful? Yes No Thank you for the feedback! All rights reserved.
0コメント