Bind9 slave server not updating
In a chroot enviroment, BIND9 has access to all the files and hardware devices it needs, but is unable to access anything it should not need.
App Armor is installed by default on recent Ubuntu releases.
This is mentioned in the BIND9 documentation "allow-transfer ....
If not specified, the default is to allow transfers to all hosts.
Unless you've explicitly disabled App Armor, you might want to read this before you decide to attempt a chrooted bind.
If you configure your registered domain to use A and B as your domain's DNS servers, then C is a Stealth Secondary.It's still a secondary, but it's not going to be asked about the zone you are serving to the internet from A and B If you configure your registered domain to use B and C as your domain's DNS servers, then A is a stealth primary.Any additional records or edits to the zone are done on A, but computers on the internet will only ever ask B and C about the zone. You can create a CNAME record pointing to another CNAME record.All that is required is simply combining the different configuration examples.There are also two other common DNS server setups (used when working with zones for registered domain names), Stealth Primary and Stealth Secondary.
Check permissions On slaves I would normally create a separate 'slaves' directory and set ownership of /var/named/slaves and /var/named/chroot/var/named/slaves to the named user via chown named /var/named/slaves Anyways, make certain that whatever user you run named as has WRITE permission to the directory /var/named since you are directing slave files to be placed there. There is no allow-transfer statement in the files on either server, so the default should be to allow. I've made sure that named user can create a file within the /var/named directory on the slave. With Springboard’s Data Science Career Track, you’ll master data science with a curriculum built by industry experts.