Secondary specification One key feature of the _D_N_S system is its ability to maintain backup copies of information about domains. The information is entered on the _p_r_i_m_a_r_y _D_N_S of a domain and copied to secondary (backup) DNSs. 11.. PPrriinncciippllee 11..11.. WWhhoo ddooeess wwhhaatt?? The information is not copied by the primary, but instead is pulled by the secondaries. The rules however, are set by the primary (see the section about secondaries requirements in the primary specification screen). Clearly, the secondary DNS administrator has to tell his DNS to act as a secondary for a given domain, but the primary DNS will tell it how! 11..22.. SSeerriiaall nnuummbbeerr The secondary will regularly talk (as told by the primary) to the primary and check the serial number (revision number) of the domain. If the serial number of the primary is the same as the copy of the secondary, or is smaller, no copy will be made. A common error is to forget to update the serial number (SOA record). Secondaries won't copy the new information. This may lead to strange behavior. _L_i_n_u_x_c_o_n_f manages serial numbers automatically! 22.. TTaasskk The secondary specification is simple. You give a domain name and the IP number of the primary DNS for that domain, followed (optionally) by alternative IP numbers, just in case the first one fails. That's it. _L_i_n_u_x_c_o_n_f takes care of setting a file name so the backup information will be stored. 33.. SShhoouulldd II tteellll MMoomm?? Someone has to tell others that your _D_N_S is the secondary of a given domain. If it's not done, then your _D_N_S is possibly working for nothing: it won't receive any query for that domain. This job must be done in the primary specification (see DNS advertising). So, if your DNS is a secondary, it is not your job :-) The primary must explicitly name the secondaries. Further, it has to register this information in the DNS of its parent domain. This is often forgotten.