Bind slave server not updating

Just another question, If I create a new zone on the master server in "named.conf", as well as the corresponding file in , do I have to manually create it on both the slave servers as well ? If not automatically created in the slave server's "named.conf", is there a way to automate it ? I will have a look into the literature that you have suggested. I carefully went through all my configs and fixed anything and everything that I could find that looked faulty or mistyped or even just left out.

So now the logs show that files are being transferred.

My largest client is getting annoyed at me, and I've tried to hack it into the code, but it's not working. User makes a change to their dns zone, and they click apply changes.

I have also disabled the iptables firewall, as that is not difficult to set up and allow port access between the 3 servers.

I just wanted to cut that out of the equation to make sure DNS and replication is working. I also did an upgrade of all 3 servers, thanks for that.

While checking the file I see that the zone entry has not been updated at slave server.

If I update it manually and reload named on slave then zone files (db files) are getting created without any issue and any modification at master server for the zone records are also getting updated.

Could you maybe point me into a direction where I can find a script that can convert this: I think you might need to have an also-notify ;line in your options stanza on the master server (with x.x.x.x being the IPs of your slave servers).

Also I have 'notify explicit' so that only those servers named in the also-notify get notified.

Once I edit the slave server file manually and add the zone entry for the newly registered/created domain and reload named then db files are getting created without any issue. Again I am mentioning it here why zone record are not getting appended to at slave server when I add a new domain name at master server.

Are we talking Zone records or new zone file altogether here?

Jan 28 ns2 named[1445]: transfer of 'yourdomain.com/IN' from 10.2.37.202#53: connected using 10.2.37.214#50135Jan 28 ns2 named[1445]: dumping master file: slaves/tmp-9Pbqi Su0dz: open: file not found Jan 28 ns2 named[1445]: transfer of 'yourdomain.com/IN' from 10.2.37.202#53: failed while receiving responses: file not found Jan 28 ns2 named[1445]: transfer of 'yourdomain.com/IN' from 10.2.37.202#53: end of transfer Jan 28 ns3 named[1466]: zone yourdomain.com/IN: Transfer started.

Jan 28 ns3 named[1466]: transfer of 'yourdomain.com/IN' from 10.2.37.202#53: connected using 10.2.37.225#52508Jan 28 ns3 named[1466]: dumping master file: slaves/tmp-9r9qwh Sw Sj: open: file not found Jan 28 ns3 named[1466]: transfer of 'yourdomain.com/IN' from 10.2.37.202#53: failed while receiving responses: file not found Jan 28 ns3 named[1466]: transfer of 'yourdomain.com/IN' from 10.2.37.202#53: end of transfer Jan 28 ns1 named[1465]: client 10.2.37.225#37852: transfer of 'yourdomain.com/IN': AXFR started Jan 28 ns1 named[1465]: client 10.2.37.225#37852: transfer of 'yourdomain.com/IN': AXFR ended Jan 28 ns1 named[1465]: client 10.2.37.225#49387: bad zone transfer request: '10.2.37.202/IN': non-authoritative zone (NOTAUTH)Jan 28 ns1 named[1465]: client 10.2.37.214#39761: transfer of 'yourdomain.com/IN': AXFR started Jan 28 ns1 named[1465]: client 10.2.37.214#39761: transfer of 'yourdomain.com/IN': AXFR ended Jan 28 ns1 named[1465]: client 10.2.37.214#57885: bad zone transfer request: '10.2.37.202/IN': non-authoritative zone (NOTAUTH)tcp 0 0 10.2.37.2 0.0.0.0:* LISTEN 1466/namedtcp 0 0 127.0.0. 0.0.0.0:* LISTEN 1466/namedtcp 0 0 127.0.0.3 0.0.0.0:* LISTEN 1466/namedtcp 0 0 :::22 :::* LISTEN 1136/sshdtcp 0 0 ::3 :::* LISTEN 1466/nameddrwxrwxr-x 2 named named 4096 Aug 25 2004 data-rwxrwxr-x 1 named named 351 Jan 28 dbs.192.168.0-rwxrwxr-x 1 named named 413 Jan 28 dbs.yourdomain.comdrwxrwxr-x 2 named named 4096 Jan 28 slaves.

I do not think that this will handle setting up zones but it will propagate changes made in the zones that are defined on both master and slave servers.