<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Tahoma
}
--></style>
</head>
<body class='hmmessage'>
Thanks a lot Christian, but I would need a little more explanation:<br><br>What's then the difference 'in concept talking' between a slave name server and a superslave one (apart, obviously, from having a concrete row in its 'supermasters' table)?<br><br>I think my main confusion is related with the utility of 'supermasters' table. Since, we have the 'domains' table where we can put our masters. Why having to do then in another table? Is it maybe a way for making the slave more restricted?<br><br><br>> Date: Mon, 13 Sep 2010 21:16:50 +0200<br>> From: ch@zeha.at<br>> To: frankeys2@hotmail.com<br>> CC: pdns-users@mailman.powerdns.com<br>> Subject: Re: [Pdns-users] Differences between slave and superslave<br>> <br>> * Francis Ramírez Verdugo <frankeys2@hotmail.com> [100913 20:50]:<br>> > <br>> > Hi all, <br>> > <br>> > I am trying to figure out when a name server is <br>> > acting as slave and when as superslave. I mean, What is the difference which <br>> > makes it to be called in these two ways? <br>> <br>> A superslave [1] is a slave with a configured list of supermasters. How<br>> this is configured depends on the backend your're using. For the generic <br>> mysql/pgsql backend please look at [2].<br>> <br>> > BTW, I supose that the opposite scenario is between <br>> > master and supermaster. In fact seting up a name server as supermaster means <br>> > that if another one is a slave of it, actually it is a superslave. <br>> <br>> There is no special supermaster operation. Any nameserver which is<br>> able to act as a master is also a supermaster. This also holds true<br>> for other nameserver products.<br>> <br>> Christian<br>> <br>> [1] http://doc.powerdns.com/slave.html#SUPERMASTER<br>> [2] http://doc.powerdns.com/generic-mypgsql-backends.html#AEN6343<br>> <br>> -- <br>> christian hofstaedtler<br> </body>
</html>