Re: slave-not-updated

2018-08-01 Thread Sten Carlsen
Don’t forget both UDP and TCP port 53 must be open. -- Best regards Sten Carlsen No improvements come from shouting: "MALE BOVINE MANURE!!!" > On 1 Aug 2018, at 13.09, Niall O'Reilly wrote: > >> On 1 Aug 2018, at 10:01, Mohammed Ejaz wrote: >> >> Is there any way to troubleshoot

Re: slave-not-updated

2018-08-01 Thread Niall O'Reilly
On 1 Aug 2018, at 10:01, Mohammed Ejaz wrote: Is there any way to troubleshoot from the master server why there is no synchnization to one more Slave. Only partly. You may need access to the slave at some stage. Master log should record NOTIFY messages sent to all slaves. If not all desired

slave-not-updated

2018-08-01 Thread Mohammed Ejaz
I have cma.org.sa zone, configured in one master and two slaves. As follows. cma.org.sa Server: UnKnown Address: 212.119.64.3 Non-authoritative answer: cma.org.sa nameserver = ns2.cyberia.net.sa (Secondary, slave server, it is ok) cma.org.sa nameserver =