By dynamic updates zone files can (see: Zone) by DNS Request to be modified. That is faster and less than a manual editing and made possible automated operational sequence. With dynamic update in principle only zone files can be changed, which lie on a master server.
A master, which receives one dynamic update Request, stores this first, before it modifies the zone file. Thus will on the one hand avoided inconsistencies with the crash of the server, on the other hand can updates be first collected in such a way, whereby a performance gain results. With the binding name server in addition per zone file a so-called journal file is put on. The collecting phase can take several minutes, so that dynamic updates are passed on often not immediately to possibly existing Slaves (by Notify and incremental zone transfer).
The dynamic update procedure is considered as safety risk. If no appropriate precautions are taken, each DNS participant can change as desired entries on the master. (More insufficiently) a minimum protection consists in the mechanism by ACCESS lists, which define exactly, of which IP address from changes to be made may. Since IP addresses can be easily falsified by UDP Messages, a Authentifizierung should being e.g. used like TSIG. A Firewall offers protection only if the master is completely shielded from the external world and communicates only with its Slaves.
The dynamic update procedure is described by the RFC 2136.
We found here 15 articles.
We found here 5 related websites.
Index | Privacy | Terms Of Use | Sitemap | Feedback