Bv9ARM.7.html revision 9bff67898d55cddfcec9ce30cc2b1bb6211ec691
2654012f83cec5dc15b61dfe3e4a4915f186e7a6Reza Sabdar<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML EXPERIMENTAL 970324//EN">
2654012f83cec5dc15b61dfe3e4a4915f186e7a6Reza Sabdar - Copyright (C) 2000 Internet Software Consortium.
2654012f83cec5dc15b61dfe3e4a4915f186e7a6Reza Sabdar - Permission to use, copy, modify, and distribute this software for any
2654012f83cec5dc15b61dfe3e4a4915f186e7a6Reza Sabdar - purpose with or without fee is hereby granted, provided that the above
2654012f83cec5dc15b61dfe3e4a4915f186e7a6Reza Sabdar - copyright notice and this permission notice appear in all copies.
2654012f83cec5dc15b61dfe3e4a4915f186e7a6Reza Sabdar - THE SOFTWARE IS PROVIDED "AS IS" AND INTERNET SOFTWARE CONSORTIUM DISCLAIMS
2654012f83cec5dc15b61dfe3e4a4915f186e7a6Reza Sabdar - ALL WARRANTIES WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES
2654012f83cec5dc15b61dfe3e4a4915f186e7a6Reza Sabdar - OF MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL INTERNET SOFTWARE
2654012f83cec5dc15b61dfe3e4a4915f186e7a6Reza Sabdar - CONSORTIUM BE LIABLE FOR ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL
2654012f83cec5dc15b61dfe3e4a4915f186e7a6Reza Sabdar - DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR
2654012f83cec5dc15b61dfe3e4a4915f186e7a6Reza Sabdar - PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS
2654012f83cec5dc15b61dfe3e4a4915f186e7a6Reza Sabdar - ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS
2654012f83cec5dc15b61dfe3e4a4915f186e7a6Reza Sabdar<META NAME="GENERATOR" CONTENT="Adobe FrameMaker 5.5/HTML Export Filter">
2654012f83cec5dc15b61dfe3e4a4915f186e7a6Reza Sabdar<TITLE> Section 7. Troubleshooting</TITLE></HEAD>
2654012f83cec5dc15b61dfe3e4a4915f186e7a6Reza SabdarSection 7. Troubleshooting</H1>
2654012f83cec5dc15b61dfe3e4a4915f186e7a6Reza Sabdar7.1 Common Log Messages and What They Mean</H3>
2654012f83cec5dc15b61dfe3e4a4915f186e7a6Reza Sabdarlame server</H6>
2654012f83cec5dc15b61dfe3e4a4915f186e7a6Reza Sabdar<PRE CLASS="2Level-fixed"><A NAME="pgfId=997353"></A>
2654012f83cec5dc15b61dfe3e4a4915f186e7a6Reza Sabdar<CODE CLASS="grammar_literal">ns named[111]: Lame server on 'www.example.com' (in 'example.com'?): [192.168.0.2].53 'ns2.example.com'</CODE>
2654012f83cec5dc15b61dfe3e4a4915f186e7a6Reza SabdarThis is a harmless error message. It means that the server at 192.168.0.2 (<EM CLASS="pathname">
2654012f83cec5dc15b61dfe3e4a4915f186e7a6Reza Sabdar) is listed as a nameserver for "<EM CLASS="pathname">
2654012f83cec5dc15b61dfe3e4a4915f186e7a6Reza Sabdar", but it doesn't really know anything about <EM CLASS="pathname">
2654012f83cec5dc15b61dfe3e4a4915f186e7a6Reza SabdarIf this is a zone under your control, check each of the nameservers to ensure that they are configured to answer questions properly.</P>
2654012f83cec5dc15b61dfe3e4a4915f186e7a6Reza SabdarIf it's a zone out on the Internet, it would be nice to notify the owners of the domain in question so that they can take a look at it. In practice, though, not many people have time to do this.</P>
2654012f83cec5dc15b61dfe3e4a4915f186e7a6Reza Sabdarbad referral</H6>
2654012f83cec5dc15b61dfe3e4a4915f186e7a6Reza Sabdar<PRE CLASS="2Level-fixed"><A NAME="pgfId=997358"></A>
2654012f83cec5dc15b61dfe3e4a4915f186e7a6Reza Sabdar<CODE CLASS="grammar_literal">ns named[111]: bad referral (other.com !< subdomain.other.com)</CODE>
2654012f83cec5dc15b61dfe3e4a4915f186e7a6Reza SabdarThis indicates that your nameserver (<EM CLASS="pathname">
2654012f83cec5dc15b61dfe3e4a4915f186e7a6Reza Sabdar) queried the nameserver for <EM CLASS="pathname">
2654012f83cec5dc15b61dfe3e4a4915f186e7a6Reza Sabdar, so your nameserver queried that.</P>
2654012f83cec5dc15b61dfe3e4a4915f186e7a6Reza Sabdar had been delegated to it, so it referred your server (<EM CLASS="pathname">
2654012f83cec5dc15b61dfe3e4a4915f186e7a6Reza Sabdar nameserver.</P>
2654012f83cec5dc15b61dfe3e4a4915f186e7a6Reza Sabdarnot authoritative for</H6>
2654012f83cec5dc15b61dfe3e4a4915f186e7a6Reza Sabdar<PRE CLASS="2Level-fixed"><A NAME="pgfId=997362"></A>
2654012f83cec5dc15b61dfe3e4a4915f186e7a6Reza Sabdar<CODE CLASS="grammar_literal">ns named-xfer[111]: [192.168.0.1] not authoritative for example.com, SOA query got rcode 0, aa 0, ancount 1, aucount 0</CODE>
2654012f83cec5dc15b61dfe3e4a4915f186e7a6Reza SabdarThis error usually shows up on a slave server. It indicates that the master server is not answering authoritatively for the zone. This usually happens when the zone is rejected (while <CODE CLASS="Program-Process">
2654012f83cec5dc15b61dfe3e4a4915f186e7a6Reza Sabdar is loading) on the master server. Check the logs on the master server. If ancount -- 0, you may be pointing at the wrong master server for the zone.</P>
2654012f83cec5dc15b61dfe3e4a4915f186e7a6Reza Sabdarrejected zone</H6>
2654012f83cec5dc15b61dfe3e4a4915f186e7a6Reza Sabdar<PRE CLASS="2Level-fixed"><A NAME="pgfId=997365"></A>
2654012f83cec5dc15b61dfe3e4a4915f186e7a6Reza Sabdar<CODE CLASS="grammar_literal">ns named[111]: master zone "example.com" (IN) rejected due to errors (serial111)</CODE>
2654012f83cec5dc15b61dfe3e4a4915f186e7a6Reza Sabdar zone was rejected because of an error in the zone file. Check the lines above this error. <CODE CLASS="Program-Process">
2654012f83cec5dc15b61dfe3e4a4915f186e7a6Reza Sabdar will usually tell you what it didn't like and where to find it in the zone file.</P>
2654012f83cec5dc15b61dfe3e4a4915f186e7a6Reza Sabdarno NS RRs found</H6>
2654012f83cec5dc15b61dfe3e4a4915f186e7a6Reza Sabdar<PRE CLASS="2Level-fixed"><A NAME="pgfId=997368"></A>
2654012f83cec5dc15b61dfe3e4a4915f186e7a6Reza Sabdar<CODE CLASS="grammar_literal">ns named[111]: Zone "example.com" (file example.com.db): no NS RRs found at zonetop</CODE>
2654012f83cec5dc15b61dfe3e4a4915f186e7a6Reza Sabdar file is missing NS records at the top of the zone (in the SOA section). Check to make sure they exist and that there is white space (spaces or tabs) in front of them. White spaces matter here.</P>
2654012f83cec5dc15b61dfe3e4a4915f186e7a6Reza Sabdarno default TTL set</H6>
2654012f83cec5dc15b61dfe3e4a4915f186e7a6Reza Sabdar<PRE CLASS="2Level-fixed"><A NAME="pgfId=997371"></A>
2654012f83cec5dc15b61dfe3e4a4915f186e7a6Reza Sabdar<CODE CLASS="grammar_literal">ns named[111]: Zone "example.com" (file example.com.db): No default TTL set using SOA minimum instead</CODE>
2654012f83cec5dc15b61dfe3e4a4915f186e7a6Reza SabdarYou will need to add a <KBD CLASS="Literal-user-input">
2654012f83cec5dc15b61dfe3e4a4915f186e7a6Reza Sabdar zone file. See RFC 2308, or <A HREF="Bv9ARM.5.html#19693" CLASS="XRef">
2654012f83cec5dc15b61dfe3e4a4915f186e7a6Reza SabdarSetting TTLs</A>
2654012f83cec5dc15b61dfe3e4a4915f186e7a6Reza Sabdar for information on how to use <CODE CLASS="grammar_literal">
2654012f83cec5dc15b61dfe3e4a4915f186e7a6Reza Sabdarno root nameserver for class</H6>
2654012f83cec5dc15b61dfe3e4a4915f186e7a6Reza Sabdar<PRE CLASS="2Level-fixed"><A NAME="pgfId=997374"></A>
2654012f83cec5dc15b61dfe3e4a4915f186e7a6Reza Sabdar<CODE CLASS="grammar_literal">findns: No root nameservers for class IN?</CODE>
2654012f83cec5dc15b61dfe3e4a4915f186e7a6Reza SabdarYour nameserver is having problems finding the root nameservers. Check your root hints file to make sure it is not corrupted. Also, make sure that your nameserver can reach the Internet.</P>
2654012f83cec5dc15b61dfe3e4a4915f186e7a6Reza SabdarIf you are running an internal root nameserver, make sure it is configured properly and is answering queries.</P>
2654012f83cec5dc15b61dfe3e4a4915f186e7a6Reza Sabdaraddress already in use</H6>
2654012f83cec5dc15b61dfe3e4a4915f186e7a6Reza Sabdar<PRE CLASS="2Level-fixed"><A NAME="pgfId=997378"></A>
2654012f83cec5dc15b61dfe3e4a4915f186e7a6Reza Sabdar<CODE CLASS="grammar_literal">ctl_server: bind: Address already in use</CODE>
2654012f83cec5dc15b61dfe3e4a4915f186e7a6Reza SabdarThis usually indicates that another copy of BIND is already running. Verify that you have killed old copies of the daemon.</P>
2654012f83cec5dc15b61dfe3e4a4915f186e7a6Reza SabdarThis can also pop up if you originally ran named as "root" and now run it as a regular user. named may have left behind an ndc control socket that is owned by root if it crashed, or was not killed gracefully.</P>
2654012f83cec5dc15b61dfe3e4a4915f186e7a6Reza SabdarThis means that the regular user wouldn't be able to delete it, so it would think named is still running. The solution is to remove any ndc sockets in <EM CLASS="pathname">
2654012f83cec5dc15b61dfe3e4a4915f186e7a6Reza Sabdar7.2 Common Problems</H3>
The best solution to solving installation and configuration issues is to take preventative measures by setting up logging files beforehand (see the sample configurations in <A HREF="Bv9ARM.3.html#30164" CLASS="XRef">
). 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>
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 secondary server is lower than the serial number on the primary, the secondary server will attempt to update its copy of the zone.</P>
Setting the serial number to a lower number on the primary server than the secondary server means that the secondary will not perform updates to its copy of the zone.</P>
The solution to this is to add 2147483647 (2^31-1) to the number, reload the zone and make sure all secondaries 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>
The Internet Software Consortium (ISC) offers a wide range of support and service agreements for BIND and DHCP servers. Four levels of premium support are available and each level includes support for all ISC programs, significant discounts on products and training, and a recognized priority on bug fixes and non-funded feature requests. In addition, ISC offers a standard support agreement package which includes services ranging from bug fix announcements to remote support. It also includes training in BIND and DHCP.</P>