dlint(1) [debian man page]

DLINT(1)						      General Commands Manual							  DLINT(1)

NAME

       dlint - Internet Domain Name System (DNS) error checking utility

SYNOPSIS

       dlint [ -n ] zone

DESCRIPTION

       DNS  administrators  can  use dlint to scan recursively through the domain records of the fully-qualified zone zone, to get a report on any
       errors therein.	You can scan a zone you own, or anyone else's zone on the Internet.  dlint talks directly to a primary or secondary  name-
       server for the zone, to make sure it's working with up-to-date information.

       dlint also suggests ways of fixing problems instead of just complaining about them like other debugging tools.

       The argument zone should always have an ending period to indicate it is a fully qualified domain name.

OPTIONS

       By default, dlint recursively traverses the entire hierarchy below the zone specified.  The -n option may be used to disable recursive tra-
       versal, causing it to only examine the records in the given zone.  Note that a zone may or may not contain any number of  sub-domains  (all
       of which will be checked with or without this option).

EXAMPLES

	      example% dlint nau.edu.

       recursively scans the DNS records in zone nau.edu for problems.

	      example% dlint 64.114.134.in-addr.arpa.

       recursively  scans  the DNS records associated with IP subnet 134.114.64.0 for problems.  You had to already know that 134.114.0.0 was sub-
       netted.

DIAGNOSTICS

       The output from dlint is computer parsable, each line has a special meaning.  Lines beginning with  a  semicolon  (;)  are  comments  only.
       Lines  beginning  with  the phrase ``WARNING'' are useful information that you should consider.	A warning is not necessarily an error, but
       may be a problem.  Lines beginning with the phrase ``ERROR'' are definite errors and should be dealt with accordingly.

EXIT STATUS

       0      Successful run, no problems encountered with zone.

       1      Successful run, worst problem with zone was a WARNING.

       2      Successful run, worst problem with zone was an ERROR.

       3      Usage error.

       4      A signal interrupted the program run (i.e. user typed interrupt key sequence).

BUGS

       Dlint doesn't work behind some firewalls because it needs to talk to a root nameserver to get started.

       Dlint uses the zone transfer mechanism (AXFR) which some nameservers deny to unauthorized hosts.

       Other nameservers happily return zero records instead of an error, in response to an unauthorized AXFR!	That is just wrong.

AUTHOR

       Paul Balyoz <pab@domtools.com>

DISTRIBUTION

       http://www.domtools.com/

COPYRIGHT

       Copyright (C) 1993-1998 Paul A. Balyoz <pab@domtools.com>

       This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as  published	by
       the Free Software Foundation; either version 2 of the License, or (at your option) any later version.

       This  program  is  distributed  in  the	hope  that  it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MER-
       CHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the GNU General Public License for more details.

       You should have received a copy of the GNU General Public License along with this program; if not, write to the Free  Software  Foundation,
       Inc., 675 Mass Ave, Cambridge, MA 02139, USA.

								   18 July 1998 							  DLINT(1)

Check Out this Related Man Page

named-checkzone(1)					      General Commands Manual						named-checkzone(1)

NAME

       named-checkzone - zone validity checking tool

SYNOPSIS

       class] mode] mode] outfile] directory] directory] zonename [filename]

DESCRIPTION

       is a tool for performing integrity checks on the zone contents.	It uses the same integrity checks as the daemon when loading a zone.  This
       makes useful for checking zone files before configuring them into a name server.  Zones and zone files are described in named.conf(4).

   Options
       Specify the class of the zone.

       Dump the zone file in canonical format.

       Enable debugging.

       Read the journal (if it exists) when loading the zone file.

       Perform	 checks with the specified failure mode.  Possible modes are (default), and The option is described in named.conf(4).

       Specify whether NS records should be checked to see if they are addresses.
		 Possible modes are (default), and

       Write zone output to
		 outfile .

       Enable quiet mode for exit code only.

       Print the version of
		 and exit.

       Change to directory (see chdir(2)) so that relative file names in master file directives work This is similar to the clause in

   Operands
       filename  The file to use for checking the zone contents.  The default is the file with the zone name.  For the default to work,  the  file
		 name for the zone in the statement of the file must be identical to the zone name.

       zonename  The zone whose contents are to be checked.

RETURN VALUE

       sets the exit status to:

	      Success.

	      Errors were detected.

EXAMPLES

       To perform integrity checks on zone in the zone file and display debug information:

AUTHOR

       was developed by the Internet Systems Consortium (ISC).

SEE ALSO

       named(1M), chdir(2), named.conf(4).

       Requests for Comments (RFC): 1035, available online at

       available online at

       available from the Internet Systems Consortium at

								     BIND 9.3							named-checkzone(1)

Linux and UNIX Man Pages

dlint(1) [debian man page]

Check Out this Related Man Page