Good Afternoon,
It's time that I ask for advice on setting up a Secondary DNS server.
I have DNS working on 5.10 Scalr. It's pretty elegant (BIND9) and allows
for entries made into the WebUI to appear in the
*/var/named/etc/bind/client_zones/* directory along with a list of all the
zones in a */var/named/etc/bind/client_zones/zones.include *file.
client_zones/
├── cloud.mydomain.com.db
├── integrations.mydomain.com.db
├── sharepoint.integrations.mydomain.com.db
├── mydomain.com.db
└── zones.include
The *zones.include* file then has an entry pointing to each zone.
//sharepoint.integrations.mydomain.com-BEGIN
zone "sharepoint.integrations.mydomain.com" {
type master;
file "client_zones/sharepoint.integrations.mydomain.com.db";
allow-transfer { none; };
};
//sharepoint.integrations.domain.com-END
But what about the secondary server? All of the above magic works because
scripts populate the files. On a Secondary DNS server we need to replicate
everything done on the primary, but with some thing like references to
allow the two to talk.
Has anyone worked this out yet, or is this green field work for me to do ?
Thanks.
--
You received this message because you are subscribed to the Google Groups
"scalr-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
