zoneserver(8) [debian man page]
ZONESERVER(8) zoneserver ZONESERVER(8) NAME
zoneserver - handle zone transfers and other TCP functions for MaraDNS DESCRIPTION
zoneserver listens on port 53/tcp and handles DNS zone transfers and any DNS query done over TCP instead of UDP. zoneserver uses a configuration file, /etc/mararc by default, to determine its parameters. USAGE
zoneserver -f pointer_to_mararc_file OPTIONS
-f Specifies the location of the configuration file. MaraDNS uses the same configuration file for both the main dns server and the zoneserver. CONFIGURATION FILE FORMAT
The file format for the mararc file can be found in the mararc(5) manual page. In particular, the zoneserver uses the zone_transfer_acl, tcp_convert_acl, tcp_convert_server, bind_address, and recursive_acl mararc parameters. EXAMPLE MARARC FILE
In this example mararc file, which is used both by maradns and zoneserver, we allow 10.1.2.3, 10.1.14.7, and 192.168.116.{any} to transfer zones, and we allow anyone on the internet to perform TCP queries. The only zone served in this example is example.com: ipv4_bind_addresses = "10.1.1.1" # Our IP tcp_convert_server = "10.1.1.1" # IP of UDP DNS server tcp_convert_acl = "0.0.0.0/0" # Anyone may do DNS-over-TCP chroot_dir = "/etc/maradns" # Where zone files are csv2 = {} # Initialize list of zone files csv2["example.com."] = "db.example.com" # example.com zone file # The next line is a list of who can transfer zones from us zone_transfer_acl = "10.1.2.3, 10.1.14.7, 192,168.116.0/24" SEE ALSO
The man pages maradns(8) and mararc(5) http://www.maradns.org BUGS
zoneserver assumes that the authoritative NS records are immediately after the SOA record, and that there is at least one non-NS between that last authority NS record for the zone and the first delegation NS record. IXFR requests are incremental zone transfers, meaning that the DNS server should only display records changed since the last IXFR request. zoneserver, however, treats an IXFR as if it were an AXFR request, outputting all of the records for the zone in question. zoneserver closes the TCP connection after transferring the requested zone. If an unauthorized client attempts to connect to the zoneserver, zoneserver immediately disconnects the unauthorized client. LEGAL DISCLAIMER
THIS SOFTWARE IS PROVIDED BY THE AUTHORS ''AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHORS OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. AUTHOR
MaraDNS is written by Sam Trenholme. Jaakko Niemi used 5 minutes to put the original version this manpage together. Sam has subsequently revised this manual page. October 2001 zoneserver ZONESERVER(8)
Check Out this Related Man Page
BIND8_NAMED2DLF.IN(1) LogReport's Lire Documentation BIND8_NAMED2DLF.IN(1) NAME
bind8_named2dlf - convert BIND8 named logs into dlf format SYNOPSIS
bind8_named2dlf DESCRIPTION
This script converts each line in a BIND8 named log to a dnszone dlf record. It is tested using Bind 8.2 logs. We're not aware of any changes in the logging format in any Bind 8.* version, we expect any bind 8.* log to get processed fine by this script. The following lines are recognized: o approved/denied AXFR requests o completed zone transfers o loaded master and slave zones o denied dynamic DNS updates DLF format The DLF format of the dnszone superservice is server Name of the DNS server time Timestamp for the request axfr_host IP address of the host requesting the AXFR axfr_zone Name of the zone being requested axfr_what approved, denied or axfr loaded_zone Name of the zone just loaded loaded_serial Serial of the zone just loaded loaded_role master or slave updatedenied_host IP address of the host requesting the update updatedenied_zone Name of the zone being updated Due to the nature of the different meanings of the lines in the logfile (not every line has both a AXFR-request, loaded a zone and gotten an update request), one or more fields can be replaced by a 0 or a -. These fields are automaticly filtered out for the different kind of reports. Example of DLF lines are: AXFR approved tim 1026644876 10.10.10.1 algron.com approved - 0 - - - update denied tim 1026645567 - - - - 0 - 10.in-addr.arpa 10.199.16.218 master zone loaded tim 1026525210 - - - nigelbowen.com.au 2002071301 master - - EXAMPLES
To process a log as produced by bind8: $ bind8_named2dlf < named-log bind8_named2dlf will be rarely used on its own, but is more likely called by lr_log2report: $ lr_log2report bind8_named < /var/log/named SEE ALSO
bind8-query2dlf(1) bind9-query2dlf(1) VERSION
$Id: bind8_named2dlf.in,v 1.7 2004/10/13 10:17:27 vanbaal Exp $ COPYRIGHT
Copyright (C) 2002 Edwin Groothuis <edwin@mavetju.org> Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: 1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. 2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. 3. The name of the copyright holder may not be used to endorse or promote products derived from this software without specific prior written permission. THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. AUTHOR
Edwin Groothuis <edwin@mavetju.org> Lire 2.1.1 2006-07-23 BIND8_NAMED2DLF.IN(1)