<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Dns on the bin</title><link>https://thebin.net/tags/dns/</link><description>Recent content in Dns on the bin</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Wed, 25 Jun 2014 00:00:00 +0000</lastBuildDate><atom:link href="https://thebin.net/tags/dns/index.xml" rel="self" type="application/rss+xml"/><item><title>BIND 9: Configure Slave Zones</title><link>https://thebin.net/2014/06/bind-9-configure-slave-zones/</link><pubDate>Wed, 25 Jun 2014 00:00:00 +0000</pubDate><guid>https://thebin.net/2014/06/bind-9-configure-slave-zones/</guid><description>&lt;p&gt;Today we are going over one of the fundamental aspects of administering a DNS infrastructure, that is maintaining consistency across multiple replicas.  The simplest method of accomplishing this is to have a master/slave relationship.  Essentially you have a read-write (master) copy and a read-only (slave) copy of the zone.  The slave looks to the master for information on changes.&lt;/p&gt;&#10;&lt;p&gt;Basic BIND Configuration&lt;/p&gt;&#10;&lt;p&gt;Here we are going to look at the key components of a BIND configuration, this should be the same regardless of if this is a master or a slave server.&lt;/p&gt;</description></item></channel></rss>