Bind9 slave not updating who is chance and real dating
masters-list may be used to reference a list of servers (slaves) defined in a masters clause each of which will be sent a NOTIFY.The key-name field defines the key to be used to authenticate the NOTIFY when using TSIG and references the name of a key clause; a corresponding key clause with the same key-name must be present in the slave server(s) for the zone.By default BIND9 will send NOTIFY messages to all the target names (right-hand names) that appear in NS RRs for the zone (this behaviour can be modified by the notify statement.
The default behaviour is to allow zone transfers to any host.
The gp-num parameter changes the port number used for NOTIFY for all the listed servers (the default is port 53).
The p-num parameter changes the port number for the specific IP address only.
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. Learn how to calculate your overhead burden using our free interactive tool and use it to determine the right price for your IT services. I didn't see your post as I was responding to the one before.
Do you wonder if your IT business is truly profitable or if you should raise your prices? Zone transfer should be allowed ONLY to TRUSTED DNS servers. The config samples I provided are from working dns master-slave servers , BIND 9, Free BSD Thanks for your reply asavah.
Search for bind9 slave not updating:
This statement is mutually exclusive with update-policy and applies to master zones only.