BIND 9.13.x is the BETA version of BIND 9.14.0
Hello BIND-users, Prior to BIND 9.13, new feature development releases were tagged as "alpha" and "beta", leading up to the first stable release for a given development branch, which always ended in ".0". Now, however, BIND has adopted the "odd-unstable/even-stable" release numbering convention. There will be no "alpha" or "beta" releases in the 9.13 branch, only increasing version numbers. The first stable release from this development branch will be renamed as 9.14.0. We plan to pull a 9.14.0 stable branch at the end of 2018. Therefore, we are already in the ‘Beta’ test period for 9.14.0. Major new features include the Local copy of the root zone feature and QNAME minimization, in particular, as well as IDNA2008 support. We want the 9.14 branch to be stable with the .0 release, and we want these new features to be well-tested and deployable. So far we have gotten two very welcome beta test reports: - Test feedback on the root zone mirror feature from Tony Finch (https://gitlab.isc.org/isc-projects/bind9/issues/375) - Thomas Jach reported an issue with QNAME minimization (https://gitlab.isc.org/isc-projects/bind9/issues/361) If you have the time and want to help us out, please consider testing 9.13 and giving us your feedback. We welcome anyone to open a BIND issue at https://gitlab.isc.org/isc-projects/bind9. Thank you, Victoria Risk Product Manager Internet Systems Consortium vi...@isc.org ___ Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
Re: slave-not-updated
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 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-users@lists.isc.org > 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-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
Re: slave-not-updated
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 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-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
slave-not-updated
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: (+966) 11 464 7114 Ext. 140 Mobile: (+966) 562311787 Fax: (+966) 11 465 4735 Website: http://www.cyberia.net.sa ___ Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
