<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<body bgcolor="#ffffff" text="#000000">
Mathew Hennessy schreef:
<blockquote cite="mid:email@example.com" type="cite">
I managed to get supermaster working again. One question though.
Does the server that is supermaster have to be listed in a NS record for
zone being delegated to the Slave?
I was hoping I could setup
ns1 - primary - slave
ns2 - secondary - slave
ns3 - extra -slave
ns4 - supermaster
I've been testing pdns (with an entirely different set of issues preventing
me from running a master on Solaris SPARC) and as long as the supermaster
was listed in the SOA I've been able to have it AXFR to slaves that are
defined as NS records, as long as each host is configured with the hostname
in pdns. I do not have the supermaster in a NS record, only in the SOA.
Same here. I'll elaborate on the mail earlier today.<br>
| ip | nameserver | account |<br>
| <ip of hidden ns>| ns1.yourdomain.com | internal |<br>
The ip is the ip-address of your ns4 (the hidden master), the
nameserver-column needs to contain the master-nameservername from the
SOA, which I would expect in your case to be ns1...<br>