0N/A>Troubleshooting</
TITLE 0N/ACONTENT="Modular DocBook HTML Stylesheet Version 1.79"><
LINK 0N/ATITLE="BIND 9 Administrator Reference Manual" 0N/ATITLE="BIND 9 Security Considerations" 0N/ASUMMARY="Header navigation table" 0N/A>BIND 9 Administrator Reference Manual</
TH 0N/A>Chapter 8. Troubleshooting</
H1 0N/A>Table of Contents</
B 0N/A>Incrementing and Changing the Serial Number</
A 0N/A>Where Can I Get Help?</
A 0N/A>8.1. Common Problems</
A 0N/A>8.1.1. It's not working; how can I figure out what's wrong?</
A 0N/A>The best solution to solving installation and
0N/A configuration issues is to take preventative measures by setting
0N/A up logging files beforehand. The log files provide a
0N/A source of hints and information that can be used to figure out
0N/A what went wrong and how to fix the problem.</
P 0N/A>8.2. Incrementing and Changing the Serial Number</
A 0N/A>Zone serial numbers are just numbers-they aren't date
0N/A related. A lot of people set them to a number that represents a
0N/A date, usually of the form YYYYMMDDRR. A number of people have been
0N/A testing these numbers for Y2K compliance and have set the number
0N/A to the year 2000 to see if it will work. They then try to restore
0N/A the old serial number. This will cause problems because serial
0N/A numbers are used to indicate that a zone has been updated. If the
0N/A serial number on the slave server is lower than the serial number
0N/A on the master, the slave server will attempt to update its copy of
0N/A>Setting the serial number to a lower number on the master
0N/A server than the slave server means that the slave will not perform
0N/A updates to its copy of the zone.</
P 0N/A>The solution to this is to add 2147483647 (2^31-1) to the
0N/A number, reload the zone and make sure all slaves have updated to
0N/A the new zone serial number, then reset the number to what you want
0N/A it to be, and reload the zone again.</
P 0N/A>8.3. Where Can I Get Help?</
A 0N/A>The Internet Software Consortium (<
ACRONYM 0N/A>) offers a wide range
0N/A of support and service agreements for <
ACRONYM 0N/A levels of premium support are available and each level includes
0N/A support for all <
ACRONYM 0N/A> programs, significant discounts on products
0N/A and training, and a recognized priority on bug fixes and
0N/A non-funded feature requests. In addition, <
ACRONYM 0N/A support agreement package which includes services ranging from bug
0N/A fix announcements to remote support. It also includes training in
0N/A>To discuss arrangements for support, contact
0N/AHREF="mailto:info@isc.org" 0N/ASUMMARY="Footer navigation table" > 9 Security Considerations</
TD