Bv9ARM.ch08.html revision 7aa594f0223f427f1382d77ae89aa890e5d9ff03
8a718a0c547e256edabd2c91f77ed668d1dfc7f8Evan Hunt<HTML
0c27b3fe77ac1d5094ba3521e8142d9e7973133fMark Andrews><HEAD
0c27b3fe77ac1d5094ba3521e8142d9e7973133fMark Andrews><TITLE
0c27b3fe77ac1d5094ba3521e8142d9e7973133fMark Andrews>Troubleshooting</TITLE
0c27b3fe77ac1d5094ba3521e8142d9e7973133fMark Andrews><META
29756974c585f616bb6e8233218cc385df9aeddbTinderbox UserNAME="GENERATOR"
591389c7d44e5ca20c357627dd179772cfefaaccEvan HuntCONTENT="Modular DocBook HTML Stylesheet Version 1.41"><LINK
591389c7d44e5ca20c357627dd179772cfefaaccEvan HuntREL="HOME"
591389c7d44e5ca20c357627dd179772cfefaaccEvan HuntHREF="Bv9ARM.html"><LINK
591389c7d44e5ca20c357627dd179772cfefaaccEvan HuntREL="PREVIOUS"
591389c7d44e5ca20c357627dd179772cfefaaccEvan HuntTITLE="BIND 9 Security Considerations"
591389c7d44e5ca20c357627dd179772cfefaaccEvan HuntHREF="Bv9ARM.ch07.html"><LINK
56e30ebae6fdb0bdf94419caff3a43fb2d16c5dfEvan HuntREL="NEXT"
56e30ebae6fdb0bdf94419caff3a43fb2d16c5dfEvan HuntTITLE="Appendices"
56e30ebae6fdb0bdf94419caff3a43fb2d16c5dfEvan HuntHREF="Bv9ARM.ch09.html"></HEAD
591389c7d44e5ca20c357627dd179772cfefaaccEvan Hunt><BODY
591389c7d44e5ca20c357627dd179772cfefaaccEvan HuntBGCOLOR="#FFFFFF"
591389c7d44e5ca20c357627dd179772cfefaaccEvan HuntTEXT="#000000"
4b669b69bae7dedda2faa09a7ade247499c1d49cMichał KępieńLINK="#0000FF"
4b669b69bae7dedda2faa09a7ade247499c1d49cMichał KępieńVLINK="#840084"
ALINK="#0000FF"
><DIV
CLASS="NAVHEADER"
><TABLE
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TH
COLSPAN="3"
ALIGN="center"
></TH
></TR
><TR
><TD
WIDTH="10%"
ALIGN="left"
VALIGN="bottom"
><A
HREF="Bv9ARM.ch07.html"
>Prev</A
></TD
><TD
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
></TD
><TD
WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="Bv9ARM.ch09.html"
>Next</A
></TD
></TR
></TABLE
><HR
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="chapter"
><H1
><A
NAME="ch08"
>Chapter 8. Troubleshooting</A
></H1
><DIV
CLASS="TOC"
><DL
><DT
><B
>Table of Contents</B
></DT
><DT
>8.1. <A
HREF="Bv9ARM.ch08.html#AEN3980"
>Common Problems</A
></DT
><DT
>8.2. <A
HREF="Bv9ARM.ch08.html#AEN3985"
>Incrementing and Changing the Serial Number</A
></DT
><DT
>8.3. <A
HREF="Bv9ARM.ch08.html#AEN3990"
>Where Can I Get Help?</A
></DT
></DL
></DIV
><DIV
CLASS="sect1"
><H1
CLASS="sect1"
><A
NAME="AEN3980"
>8.1. Common Problems</A
></H1
><DIV
CLASS="sect2"
><H2
CLASS="sect2"
><A
NAME="AEN3982"
>8.1.1. It's not working; how can I figure out what's wrong?</A
></H2
><P
>The best solution to solving installation and
configuration issues is to take preventative measures by setting
up logging files beforehand. The log files provide a
source of hints and information that can be used to figure out
what went wrong and how to fix the problem.</P
></DIV
></DIV
><DIV
CLASS="sect1"
><H1
CLASS="sect1"
><A
NAME="AEN3985"
>8.2. Incrementing and Changing the Serial Number</A
></H1
><P
>Zone serial numbers are just numbers-they aren't date
related. A lot of people set them to a number that represents a
date, usually of the form YYYYMMDDRR. A number of people have been
testing these numbers for Y2K compliance and have set the number
to the year 2000 to see if it will work. They then try to restore
the old serial number. This will cause problems because serial
numbers are used to indicate that a zone has been updated. If the
serial number on the slave server is lower than the serial number
on the master, the slave server will attempt to update its copy of
the zone.</P
><P
>Setting the serial number to a lower number on the master
server than the slave server means that the slave will not perform
updates to its copy of the zone.</P
><P
>The solution to this is to add 2147483647 (2^31-1) to the
number, reload the zone and make sure all slaves have updated to
the new zone serial number, then reset the number to what you want
it to be, and reload the zone again.</P
></DIV
><DIV
CLASS="sect1"
><H1
CLASS="sect1"
><A
NAME="AEN3990"
>8.3. Where Can I Get Help?</A
></H1
><P
>The Internet Software Consortium (<SPAN
CLASS="acronym"
>ISC</SPAN
>) offers a wide range
of support and service agreements for <SPAN
CLASS="acronym"
>BIND</SPAN
> and <SPAN
CLASS="acronym"
>DHCP</SPAN
> servers. Four
levels of premium support are available and each level includes
support for all <SPAN
CLASS="acronym"
>ISC</SPAN
> programs, significant discounts on products
and training, and a recognized priority on bug fixes and
non-funded feature requests. In addition, <SPAN
CLASS="acronym"
>ISC</SPAN
> offers a standard
support agreement package which includes services ranging from bug
fix announcements to remote support. It also includes training in
<SPAN
CLASS="acronym"
>BIND</SPAN
> and <SPAN
CLASS="acronym"
>DHCP</SPAN
>.</P
><P
>To discuss arrangements for support, contact
<A
HREF="mailto:info@isc.org"
TARGET="_top"
>info@isc.org</A
> or visit the
<SPAN
CLASS="acronym"
>ISC</SPAN
> web page at <A
HREF="http://www.isc.org/services/support/"
TARGET="_top"
>http://www.isc.org/services/support/</A
>
to read more.</P
></DIV
></DIV
><DIV
CLASS="NAVFOOTER"
><HR
ALIGN="LEFT"
WIDTH="100%"><TABLE
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="Bv9ARM.ch07.html"
>Prev</A
></TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="Bv9ARM.html"
>Home</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="Bv9ARM.ch09.html"
>Next</A
></TD
></TR
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
><SPAN
CLASS="acronym"
>BIND</SPAN
> 9 Security Considerations</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
>&nbsp;</TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>Appendices</TD
></TR
></TABLE
></DIV
></BODY
></HTML
>