slave-not-updated

[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 = ns1.medu.net.sa ( third slave, changes are not
updated with serial change)

cma.org.sa nameserver = ns1.cyberia.net.sa (this is the master server)



ns1.medu.net.sa internet address = 213.230.0.10

ns1.cyberia.net.sa internet address = 212.119.92.5

ns2.cyberia.net.sa internet address = 212.119.93.5



When I enable the logs for xfer, it doesn't give any clue of problem name
server of medun.net.sa.



Is there any way to troubleshoot from the master server why there is no
synchnization to one more Slave.



Thanks in advance.



Thanks,

Mohammed Ejaz

Asst. Operation Director of Systems.

Cyberia SAUDI ARABIA

P.O.Box: 301079, Riyadh 11372

Phone: [phone] Ext. 140

Mobile: [phone]

Fax: [phone]

Website: http://www.cyberia.net.sa

[Niall O'Reilly]

Post by Mohammed Ejaz
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 slaves are being sent NOTIFY, master needs to be
configured with relevant directive (BIND named: also-notify).

If master is sending NOTIFY, next thing to check is whether slave
is requesting AXFR/IXFR. Master log should show each transfer.
If not, then you’ll need to ask sysadmin at slave to check whether
NOTIFY is arriving and being accepted, and whether slave is actually
requesting transfer. If not, slave configuration may need
correction (BIND named: allow-notify).

If there is still a problem, you’ll likely need to use tcpdump or
the like to investigate at network level, as NOTIFY or transfer
may be blocked by a misconfigured firewall or other network fault.


One other thing: avoid using nslookup. In trying to be “helpful”,
it hides significant information and makes troubleshooting difficult.
You’ll save time (yours, and that of anyone who tries to help you)
by using dig.

Best regards,
Niall O’Reilly
_______________________________________________
Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list

bind-users mailing list
bind-***@lists.isc.org
h

[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!!!"

Post by Niall O'Reilly

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 slaves are being sent NOTIFY, master needs to be
configured with relevant directive (BIND named: also-notify).
If master is sending NOTIFY, next thing to check is whether slave
is requesting AXFR/IXFR. Master log should show each transfer.
If not, then you’ll need to ask sysadmin at slave to check whether
NOTIFY is arriving and being accepted, and whether slave is actually
requesting transfer. If not, slave configuration may need
correction (BIND named: allow-notify).
If there is still a problem, you’ll likely need to use tcpdump or
the like to investigate at network level, as NOTIFY or transfer
may be blocked by a misconfigured firewall or other network fault.
One other thing: avoid using nslookup. In trying to be “helpful”,
it hides significant information and makes troubleshooting difficult.
You’ll save time (yours, and that of anyone who tries to help you)
by using dig.
Best regards,
Niall O’Reilly
_______________________________________________
Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list
bind-users mailing list
https://lists.isc.org/mailman/listinfo/bind-users

_______________________________________________
Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list

bind-users mailing list
bind-***@lists.isc.org
https://lists.isc.org/mailman/